Sliding-window multi-class striping

ABSTRACT

A sequence of storage devices of a data store may include one or more stripesets for storing data stripes of different lengths and of different types. Each data stripe may be stored in a prefix or other portion of a stripeset. Each data stripe may be identified by an array of addresses that identify each page of the data stripe on each included storage device. When a first storage device of a stripeset becomes full, the stripeset may be shifted by removing the full storage device from the stripeset, and adding a next storage device of the data store to the stripeset. A class variable may be associated with storage devices of a stripeset to identify the type of data that the stripeset can store. The class variable may be increased (or otherwise modified) when a computer stores data of a different class in the stripeset.

This application is a divisional of allowed U.S. application Ser. No.14/694,891, titled “Sliding-Window Multi-Class Striping,” filed on Apr.23, 2015, which is a divisional of U.S. application Ser. No. 13/868,887,titled “Sliding-Window Multi-Class Striping,” filed on Apr. 23, 2013,now U.S. Pat. No. 9,043,546, which is a divisional of U.S. applicationSer. No. 12/426,783, titled “Sliding-Window Multi-Class Striping,” filedon Apr. 20, 2009, now U.S. Pat. No. 8,799,572, issued on Aug. 5, 2014,all of which are incorporated by reference herein in their entireties.

BACKGROUND

Computer data storage refers to components, devices, and/or recordingmedia used to retain digital data for periods of time. Various types ofcomputer data storage exist, including memory devices (e.g.,semiconductor storage), such as random access memory (RAM) devices andread only memory (ROM) devices, and mass storage devices, such asoptical discs and magnetic storage (hard disks, magnetic tapes, etc.),and further types of storage.

A particular computer data storage implementation may be associated witha single computer or may be shared by multiple computers. For instance,a computer system that includes multiple computers may share a largepersistent data store that is accessible over a storage network. Thepersistent data store may include a large number of independent storageunits, including an array of hard disk drives and/or flash memorydevices. Data may be stored in the data store in various ways. Forinstance, in one current technique for storing data, multipage units ofdata may be stored in a data store in the form of “stripes.” A set ofstorage units that is used to store data stripes may be referred to as a“stripeset.” “Stripesets” that store data in the form of “stripes”enable relatively high performance and high availability to stored data.

Allowing multiple computers to independently write stripes to astripeset can be difficult to manage, however. For example, if pages ofa stripe are written to different storage units independently, it may bedifficult to ensure that pages from different stripes are written in thesame order to all storage units of the stripeset. If stripes arepermitted to be variable length, initial storage units of a stripesetmay fill up faster than the last storage units of the stripeset.Furthermore, it may be difficult for the computers to determine anactive stripeset at boot time. Still further, it is difficult to managemultiple independent stripesets.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

A sequence of storage devices of a data store may include one or morestripesets for storing data stripes of different lengths and ofdifferent data types. Each data stripe may be stored in a prefix orother portion of a stripeset. Each data stripe may be identified by anarray of addresses that identify each page of the data stripe on eachincluded storage device. When a first storage device of a stripesetbecomes full, the stripeset may be shifted by removing the full storagedevice from the stripeset, and adding a next storage device of the datastore to the stripeset. A class variable may be associated with storagedevices of a stripeset to identify the type of data that the stripesetcan store. The class variable may be increased (or otherwise modified)when a computer stores data of a different class in the stripeset.

In a first implementation, a method is provided for identifying a datastripe. Data that includes M data pages is stored as a stripe in astripeset of a data store. The stripeset includes N storage devices. Areference is generated for the stripe that includes an identifier and avector. The identifier is an identifier for a storage device of the Nstorage devices in which a first data page of the M data pages isstored. The vector includes a page slot indicator for each of the M datapages. Each page slot indicator indicates for a corresponding data pageof the M data pages a page slot of a storage device of the N storagedevices in which the corresponding data page is stored.

The N storage devices of the stripeset may be associated in a logicalsequence. The logical sequence includes a first storage device of the Nstorage devices at a logical first end of the stripeset and a secondstorage device of the N storage devices at a logical second end of thestripeset.

The first storage device in the logical sequence may be determined to befull. The first storage device may be removed from the stripeset. A nextstorage device of the data store may be added to the stripeset to belogically positioned at the logical second end of the stripeset adjacentto the second storage device.

In another implementation, another method is provided. A class variableis associated with a corresponding storage device of a data store. Thedata store includes a plurality of storage devices having associatedclass variables. Each class variable indicates a class or store statusof the corresponding storage device. The class variable is enabled to bemodified by a computer that stores a data page of a data stripe in thecorresponding storage device. The class variable is enabled to be resetby a computer that erases data stored in the corresponding storagedevice.

For instance, a request may be received from the computer to store adata page in the storage device. The request may include a classindication. The data page is enabled to be stored in a next availablepage slot of the storage device if the class indication has a firstrelationship with the class variable associated with the storage device.The data page is enabled to be stored in a next available page slot ofthe storage device, and the class variable is enabled to be modified, ifthe class indication has a second relationship with the class variable.A response to the request is generated that includes the class variableif the class indication has a third relationship with the classvariable.

In another implementation, a method for determining a stripeset in aplurality of storage devices in a data store is provided. The storagedevices are associated in a logical sequence. The logical sequenceincludes a first storage device at a logical first end of the pluralityof storage devices and a second storage device at a logical second endof the plurality of storage devices. A logically closest non-emptystorage device of the plurality of storage devices to the logical firstend is determined. An active storage device of the plurality of storagedevices in a range of the logical sequence from the logically closestnon-empty storage device to the logical second end is determined. Acontinuous range of active storage devices in the plurality of storagedevices is determined that includes the determined active storagedevice.

In still another implementation, a method for storing a data stripe in astripeset is provided. A first set of data pages to be stored in a firststripeset of a data store is provided. The first stripeset includes Mstorage devices. The M storage devices of the first stripeset areassociated in a logical sequence that includes a first storage device ofthe M storage devices at a logical first end of the second stripeset anda second storage device of the M storage devices at a logical second endof the second stripeset. The first storage device is determined to befull. The first storage device is removed from the first stripeset. Athird storage device of the data store is added to the first stripeset.The third storage device of the data store has an associated classvariable that indicates a class of a second stripeset of the data store.The class variable is changed to indicate a class of the firststripeset. The first set of data pages is stored as a stripe in thefirst stripeset, including storing a data page of the first set of datapages in the third storage device.

Computer systems and computer program products (stored on a computerreadable medium) are also described herein that are capable ofperforming and/or enabling the methods described above and elsewhereherein, and for implementing further embodiments as described herein.

Further features and advantages of the invention, as well as thestructure and operation of various embodiments of the invention, aredescribed in detail below with reference to the accompanying drawings.It is noted that the invention is not limited to the specificembodiments described herein. Such embodiments are presented herein forillustrative purposes only. Additional embodiments will be apparent topersons skilled in the relevant art(s) based on the teachings containedherein.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

The accompanying drawings, which are incorporated herein and form a partof the specification, illustrate the present invention and, togetherwith the description, further serve to explain the principles of theinvention and to enable a person skilled in the pertinent art to makeand use the invention.

FIG. 1 shows a computing and data storage system in which a plurality ofcomputing devices access shared storage.

FIGS. 2 and 3 show example storage devices of a data store that storedata in the form of data stripes.

FIG. 4 shows a block diagram of a data store, according to exampleembodiment of the present invention.

FIG. 5 shows a flowchart providing a process for storing data in astripeset, according to an example embodiment of the present invention.

FIGS. 6 and 7 show views of the data store of FIG. 4 storing datastripes, according to example embodiments of the present invention.

FIG. 8 shows a flowchart for storing a data stripe, according to anexample embodiment of the present invention.

FIG. 9 shows a block diagram of a computer, according to an exampleembodiment of the present invention.

FIG. 10 shows a flowchart for storing a data stripe in a stripesetprefix, according to an example embodiment of the present invention.

FIG. 11 shows a flowchart providing a process for stripeset sliding,according to an example embodiment of the present invention.

FIG. 12 shows a block diagram of a data store including a slidingstripeset window, according to an example embodiment of the presentinvention.

FIG. 13 shows a block diagram of a storage device that includes a classvariable, according to an example embodiment of the present invention.

FIG. 14 shows a flowchart providing a process for handling storage in astorage device, according to an example embodiment of the presentinvention.

FIG. 15 shows a flowchart providing a process for modifying a classvariable based on a store request, according to an example embodiment ofthe present invention.

FIG. 16 shows a block diagram of a storage controller, according to anexample embodiment of the present invention.

FIG. 17 shows a block diagram of a data store, according to an exampleembodiment of the present invention.

FIG. 18 shows a block diagram of a storage device, according to anexample embodiment of the present invention.

FIG. 19 shows a flowchart providing a process for determining an activestripeset, according to an example embodiment of the present invention.

FIG. 20 shows a block diagram of a computer, according to an exampleembodiment of the present invention.

FIG. 21 shows a block diagram of a stripeset determiner module,according to an example embodiment of the present invention.

FIGS. 22, 24, and 25 shows flowcharts providing processes for performingthe flowchart of FIG. 19, according to example embodiments of thepresent invention.

FIG. 23 shows a block diagram of a data store, according to an exampleembodiment of the present invention.

FIG. 26 shows a block diagram of a data store that maintains a masterdirectory, according to an example embodiment of the present invention.

FIG. 27 shows a flowchart providing a process for generating amulticlass stripeset, according to an example embodiment of the presentinvention.

FIG. 28 shows a block diagram of a data store, according to an exampleembodiment of the present invention.

FIG. 29 shows a block diagram of storage devices having associated classvariables, according to an example embodiment of the present invention.

FIGS. 30 and 32 show block diagrams of a data store that includesmultiple stripesets that can slide and can overlap to form multiclassstripesets, according to example embodiments of the present invention.

FIG. 31 shows a flowchart providing a process for storing a data stripeand sliding a stripeset, according to an example embodiment of thepresent invention.

FIG. 33 shows a flowchart providing a process for storing a data stripeand sliding a stripeset, according to an example embodiment of thepresent invention.

FIG. 34 shows a block diagram of an example computer that may be used toimplement embodiments of the present invention.

The features and advantages of the present invention will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference charactersidentify corresponding elements throughout. In the drawings, likereference numbers generally indicate identical, functionally similar,and/or structurally similar elements. The drawing in which an elementfirst appears is indicated by the leftmost digit(s) in the correspondingreference number.

DETAILED DESCRIPTION

I. Introduction

The present specification discloses one or more embodiments thatincorporate the features of the invention. The disclosed embodiment(s)merely exemplify the invention. The scope of the invention is notlimited to the disclosed embodiment(s). The invention is defined by theclaims appended hereto.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

Furthermore, it should be understood that spatial descriptions (e.g.,“above,” “below,” “up,” “left,” “right,” “down,” “top,” “bottom,”“vertical,” “horizontal,” etc.) used herein are for purposes ofillustration only, and that practical implementations of the structuresdescribed herein can be spatially arranged in any orientation or manner.

II. Data Storage Systems

Embodiments of the present invention relate to techniques for storingdata and accessing data stored in computer data storage. Computer datastorage refers to components, devices, and/or recording media used tostore digital data. A particular computer data storage implementationmay be accessed by a single computer or may be shared by multiplecomputers. For example, FIG. 1 shows a computing and data storage system100 in which a plurality of computing devices access shared storage. Asshown in FIG. 1, system 100 includes first-third computers 102 a-102 c,a communication network 104, and a data store 106. Data store 106includes a plurality of storage units/storage devices 108 a-108 n. Inthe example of FIG. 1, first-third computers 102 a-102 c share datastore 106, including being enabled to store data in, and to access datastored in storage devices 108 a-108 n of data store 106 (through network104).

Although three computers 102 a-102 c are shown in FIG. 1, any number ofcomputers 102 may be coupled to network 100 to share data store 106,include hundreds, thousands, or even further numbers of computingdevices. Examples of computers 102 include stationary and mobilecomputing devices. For example, each of computers 102 a-102 c may be adesktop computer (e.g., a personal computer), a mobile computer (e.g., apersonal digital assistant (PDA), a laptop computer, a notebookcomputer, a smart phone, etc.), or other type of computing device.

Each of computers 102 a-102 c is shown in FIG. 1 as communicating withdata store 106 through network 104 and a corresponding communicationlink. For example, as shown in FIG. 1, computer 102 a is communicativelycoupled with network 104 through a first communication link 110 a,computer 102 b is communicatively coupled with network 104 through asecond communication link 110 b, and computer 102 c is communicativelycoupled with network 104 through a third communication link 110 c. Datastore 106 is shown communicatively coupled with network 104 through afourth communication link 110 d. Network 104 may be a LAN, WAN (widearea network), or combination of networks, such as the Internet.First-fourth communication links 110 a-110 d may include any type orcombination of communication links, including wired and/or wirelesslinks, such as IEEE 802.11 wireless LAN (WLAN) wireless links, WorldwideInteroperability for Microwave Access (Wi-MAX) links, cellular networklinks, wireless personal area network (PAN) links (e.g., Bluetooth™links), Ethernet links, USB links, etc.

Data store 106 may include storage devices 108 a in any configuration,including as an array. Although storage devices 108 a-108 n are shown inFIG. 1, any number of storage devices 108 may be included in data store106 to store data, include hundreds, thousands, or even further numbersof storage devices.

Data may be stored in data store 106 in various ways. For instance, inone current technique for storing data, multipage sets of data may bestored in data store 106 in the form of “stripes.” A “stripe” is amultipage set of data that may be stored in storage in a singleoperation, where each data page is written to a different storagedevice. Furthermore, a data stripe may be read from storage in a singleoperation. Each page of the multipage set of data is stored in acorresponding storage device, to form a “stripe” of the data across thestorage devices. Each storage device may have multiple slots for storingdata pages, including hundreds, thousands, millions, or even greaternumbers of data pages, and thus may include pages from various numbersof stripes. A set of storage devices of data store 106 that is used tostore a stripe may be referred to as a “stripeset.” A “stripeset” mayinclude any number of storage devices to store a corresponding number ofpages of data for each stripe, including hundred, thousands, or evengreater numbers of storage devices. The number of storage devicesincluded in a stripeset, corresponding to the maximum number of pagesfor a set of data that may be stored in the stripeset, may be referredto as the “rank” of the stripeset.

For example, FIG. 2 shows storage devices 108 a-108 n of data store 106storing data in the form of a stripe. As shown in FIG. 2, a first stripe204 representing data that includes three data pages 206 a-206 c isstored in data store 106. In FIG. 2, storage devices 108 a-108 d arecurrently a portion of data store 106 allocated for storing data in theform of stripes, and thus form a stripeset 202. Because in the currentexample, stripeset 202 includes four storage devices 108 a-108 d,stripes including four or less pages of data may be stored in stripeset202. Storage devices 108 e-108 n are not included in stripeset 202. Asshown in FIG. 2, stripeset 202 stores first stripe 204. First page 206 aof first stripe 204 is stored in storage device 108 a, second page 206 bof first stripe 204 is stored in storage device 108 b, and third page206 c of first stripe 204 is stored in storage device 108 c. Becausefirst stripe 204 includes three data pages, no data of first stripe 204is stored in fourth storage device 108 d of stripeset 202, and an emptypage 208 is indicated in a first page slot of storage device 108 dcorresponding to first stripe 204.

“Stripesets” that store data in the form of “stripes” enable relativelyhigh performance and high availability to stored data in data store 106.Furthermore, stripesets enable greater data security, storing dataacross multiple storage devices rather than a single storage device inwhich a single point of failure may lead to loss of all stored data. Ifone of storage devices 108 a-108 d of stripeset 202 fails, the data ofthe failing storage device may be recovered according to an errorcorrection technique, depending on the particular implementation.

Allowing multiple computers, such as computers 102 a-102 c shown in FIG.1, to independently write stripes to a stripeset, such as stripeset 202in FIG. 2, can be difficult to manage, however. For example, it may beimportant that pages from different stripes, including pages 206 a-206 cof stripe 204, are written to storage devices 108 a-108 c in a sameorder so that pages of the stripes do not become intermixed.Furthermore, if stripes are permitted to be variable length, initialstorage units of a stripeset may fill up faster than the last storageunits of the stripeset, resulting in inefficient use of storage. Forexample, FIG. 3 shows data store 106 of FIG. 2, with a second set ofdata stored in stripeset 202 as a second stripe 302. Second stripe 302includes four data pages, first-fourth data pages 304 a-304 d. As shownin FIG. 3, first page 304 a of second stripe 302 is stored in storagedevice 108 a, second page 304 b of second stripe 302 is stored instorage device 108 b, third page 304 c of second stripe 302 is stored instorage device 108 c, and fourth page 304 d of second stripe 302 isstored in storage device 108 d. As shown in FIG. 3, due to the differentpage lengths of first and second stripes 204 and 302, first-thirdstorage devices 108 a-108 c are filling up faster than storage device108 d.

Furthermore, it may be difficult for computers 102 a-102 c to determinethe location of an active stripeset in data store 106 (e.g., which ofstorage devices 108 a-108 n include stripeset 202) at boot time. Stillfurther, if multiple independent stripesets may simultaneously bepresent in data store 106 to store different types of data (e.g., binarylarge objects, indexes, logs, etc.), it may be difficult to manage themultiple stripesets.

Embodiments of the present invention overcome such deficiencies inconventional data storage systems. Examples of such embodiments aredescribed below.

III. Example Embodiments

The example embodiments described herein are provided for illustrativepurposes, and are not limiting. Furthermore, additional structural andoperational embodiments, including modifications/alterations, willbecome apparent to persons skilled in the relevant art(s) from theteachings herein.

Embodiments relate to shared storage systems, where many computers mayshare one pool of storage devices. In such a system, multiple computersmay be reading from and writing to storage devices independently. It iscomplex and expensive for the computers to synchronize their views ofthe state of all of the storage devices. It is also undesirable for allof the computers to funnel their read and/or write operations through asingle computer that functions as a storage server, because such aconfiguration may limit scalability of the system. Embodiments describedherein overcome these limitations, including enabling multiple computerto read and write to a common pool of storage independently, without thecomputers needing to synchronize their views of the state of the storagedevices.

In an embodiment, store operations are made with respect to storagedevices in a data store that are configured for “append” operations and“erase” operations. With regard to an append operation, a storage deviceidentifier and a data page are received (e.g., from a computer 102 ofFIG. 1) as an input to a storage device, a page of data is stored in thestorage device, and an address of a page slot in the storage devicewhere the page is stored is returned (e.g., to computer 102). Withregard to an erase operation, an erase command is received (e.g., from acomputer 102 of FIG. 1) as an input to a storage device, and inresponse, the storage device erases the data contents of the storagedevice. After executing an erase operation on a storage device, a nextappend operation performed at the storage device stores a received pageof data in the “first” page slot of the storage device. The append anderase operations may be implemented by each device that manages storagedevices. For example, a controller configured to implement append anderase operations may be incorporated in each storage device, or for agroup of storage devices. However, other implementations are possible,such as implementing append and erase operations in a front-end serverthat manages a group of storage devices.

FIG. 4 shows a block diagram of a data store 400, according to anexample embodiment. Computers 102 shown in FIG. 1 may communicate withdata store 400 (e.g., through network 104) to store data and access datastored in data store 400, for example. As shown in FIG. 4, data store400 includes storage devices 402 a-402 z. Any number of storage devices402 may be included in data store 400, including numbers in the ones,tens, hundreds, thousands, and even greater numbers of storage devices.Storage devices 402 a-402 z are configured to process append and eraseoperations, as described above. In an embodiment, storage devices 402a-402 z may be append-only storage devices, meaning that storage devices402 a-402 z are only configured to perform append and erase operations(e.g., are not configured to perform further types of storage-relatedoperations), but in other embodiments storage devices 402 a-402 z may beconfigured to perform further storage-related operations.

As shown in FIG. 4, each of storage devices 402 a-402 z includes asequence of page slots. For example, storage device 402 a includes pageslots 404 a-404 y, storage device 402 b includes page slots 406 a-406 y,storage device 402 c includes page slots 408 a-408 y, storage device 402d includes page slots 410 a-410 y, etc. Any number of page slots may beincluded in each storage device 402, including numbers in the ones,tens, hundreds, thousands, and even greater numbers of page slots. Eachpage slot may store one page of data of a corresponding data stripe, forexample. Furthermore, a portion or all of storage devices 402 a-402 zmay be included in one or more stripesets included in data store 400.

Storage devices 402 a-402 z may be arranged or associated in data store400 in any configuration, including as an array, in a storage areanetwork (SAN), etc. A storage device 402 may be any type of storagedevice, volatile and/or non-volatile, including a memory device and/or amass storage device. Examples of storage devices 402 include memorydevices (e.g., semiconductor storage), such as random access memory(RAM) devices (volatile or non-volatile), and read only memory (ROM)devices, and mass storage devices, such as optical discs and magneticstorage (hard disks, magnetic tapes, etc.), and further types ofstorage. Storage devices 402 may include memory devices (e.g., flashmemory devices) when faster data access is desired, and/or mass storagedevices may be present when greater storage capacity is desired. Astorage device, as defined herein, may also be referred to as a“segment” or a “storage segment.”

The following subsections describe example embodiments for storing ofdata stripes received from computers, such as computers 102 of FIG. 1,in data store 400 in the form of data stripes.

A. Example Embodiments for Storing Stripes

An example striping system may support three operations, referred to as“get-stripeset,” “store-stripe,” and “get-stripe.” A “get-stripeset”operation returns a stripeset reference, which identifies a set ofstorage devices where a stripe can be written. The number of storagedevices that are included in a stripeset is the “rank” of the stripeset.A “store-stripe” operation takes a stripeset reference and a main-memoryreference to some data to be stored and returns a stripe reference thattells where the data was stored. If there is no more space in thestripeset, then it returns a new stripeset reference in addition to thestripe reference. A “get-stripe” operation takes a stripe reference asinput and returns the data in the stripe that is identified by thatstripe reference. Such operations may be transmitted as commands tostorage devices of a data store by requesting devices, such as computers102 shown in FIG. 1.

A conventional approach to storing stripes in a stripeset is to requirethat all stripes have the same number of pages and that all pages of astripe are stored at the same page slot offset in each storage deviceforming the stripeset. For example, referring to FIG. 3, stripeset 202has a rank of four. In such case, four storage devices 108 a-108 d areincluded in stripeset 202, and each stripe has four pages. A “stripereference” that identifies first stripe 204 stored in stripeset 202 mayhave a value of one, and each data page stored in storage devices 108a-108 d is stored at an offset of one in storage devices 108 a-108 d. Astripe reference that identifies second stripe 302 stored in stripeset202 may have a value of two, and each data page of second stripe 302stored in stripeset 202 is stored at an offset of two in storage devices108 a-108 d. Due to this conventional addressing scheme, even if a datastripe to be written into stripeset 202 includes less than four pages,four data pages of storage devices 108 a-108 d are dedicated to thestripe. For example, even though the data corresponding to first stripe204 included three data pages, which are stored in storage devices 108a-108 c, an empty page 208 of storage device 108 d is included in firststripe 204. Thus, some storage devices of data store 106 may includeempty data pages when stripes stored in stripeset 202 have a length thatis less than a rank of stripeset 202, which is an inefficient use ofstorage capacity of data store 106.

In an embodiment, data stripes may be stored in storage in a manner thatdoes not result in storage devices having empty data pages when storingstripes having lengths less than a rank of a stripeset. For instance,FIG. 5 shows a flowchart 500 providing a process for storing data in astripeset, according to an example embodiment. In an embodiment,flowchart 500 may be performed by data store 400 shown in FIG. 4. Otherstructural and operational embodiments will be apparent to personsskilled in the relevant art(s) based on the discussion regardingflowchart 500. Flowchart 500 is described as follows.

As shown in FIG. 5, flowchart 500 begins with step 502. In step 502,data that includes M data pages is stored as a stripe in a stripeset ofa data store. In an embodiment, data pages of a set of data may bestored in a subset of a stripeset. For instance, a stripe that includesM pages may be stored in a stripeset of N storage devices, where N>M.The stripe is written to a subsequence of the M storage devices of thestripeset. For instance, FIG. 6 shows a block diagram of data store 400of FIG. 4, according to an example embodiment. In the example of FIG. 6,a stripeset 602 is present in data store 400 of rank four (N=4), whichincludes storage devices 402 a-402 d. A first stripe 604 is stored instripeset 602 that includes two data pages, a first data page 606 a anda second data page 606 b (M=2). In the example of FIG. 6 data pages 606a and 606 b are stored in page slots 404 a and 406 a of storage devices402 a and 402 b, respectively. However, data pages 606 a and 606 b maybe alternatively stored in page slots 406 a and 408 a of storage devices402 b and 402 c, respectively, or in page slots 408 a and 410 a ofstorage devices 402 c and 402 d, respectively. In embodiments, firststripe 604 does not consume space on storage devices of data store 602where first stripe 604 is not written. For example, first stripe 604,when stored in storage devices 402 a and 402 b, does not consume spaceon storage devices 402 c and 402 d. That is, for this case, first pageslots 408 a and 410 a of storage devices 402 c and 402 d are stillavailable to store other data.

In step 504, a reference is generated for the stripe that includes anidentifier for a storage device of the N storage devices in which afirst data page of the M data pages is stored and a vector that includesa page slot indicator for each of the M data pages. In an embodiment,data store 400 generates a stripe reference for each stripe stored instripeset 602. The stripe reference includes an identifier for the oneof storage devices 402 a-402 d in which a first data page of the datastripe is stored, and includes a vector that includes a page slotindicator for each of the M data pages of the stripe. Each page slotindicator indicates for a corresponding data page of the M data pages apage slot of a storage device 402 of the N storage devices of stripeset602 in which the corresponding data page is stored.

For example, referring to FIG. 6, first stripe 604 may have a stripereference generated that includes an identifier for storage device 402a, which is the storage device storing first data page 606 a of stripe604, and a vector indicating page slots 404 a and 406 a, which are pageslots of storage devices 402 a and 402 b, which store pages 606 a and606 b of first stripe 604. Storage device 402 a may be identified in anymanner, including by a storage device ID. For instance, each of storagedevices 402 a-402 z may be assigned a corresponding storage device ID,which may be a number that identifies each of storage devices 402 a-402z in a sequence in which they are associated in data store 400 (e.g.,data store 400 may include a thousand storage devices 402, which areassigned identifiers 1-1000, respectively, in sequence). Likewise, pageslots 404 a and 404 b may be identified in any manner, including by apage slot ID. For instance, page slots of a particular storage device,such as page slots 404 a-404 y of storage device 402 a, may be assigneda corresponding number or other identifier that identifies each pageslot 404 in a sequence in which they are stored in storage device 402 a.For example, a thousand page slots 404 in storage device 402 a may beassigned identifiers 1-1000, respectively. Thus, in an embodiment, astripe reference generated for first stripe 604 may have the form of anidentifier of “1” for storage device 402 a, and a vector of [1, 1],identifying page slots 404 a and 406 a of storage devices 402 a and 402b that store pages 606 a and 606 b of first stripe 604.

As shown in FIG. 7, a second stripe 702 may be stored in stripeset 602in addition to first stripe 604, according to step 502 of flowchart 500.In the example of FIG. 7, second stripe 702 includes four data pages,first-fourth data page 704 a-704 d (M=4). In the example of FIG. 7 datapages 704 a-704 d are stored in page slots 404 b, 406 b, 408 a, and 410a of storage devices 402 a-402 d, respectively. This is in contrast to aconventional approach, where data pages 704 a-704 d would be stored inthe second page slot of each of storage devices 402 a-402 d (page slots404 b, 406 b, 408 b, and 410 b) even though pages slots 408 a and 408 bwere empty, leading to an inefficient utilization of storage space.

According to step 504 of flowchart 500, a stripe reference may begenerated for second stripe 702. In an embodiment, the stripe referencegenerated for second stripe 702 may be an identifier of “1” for storagedevice 402 a, and a vector of [2, 2, 1, 1], identifying page slots 404b, 406 b, 408 a, and 410 a as storing pages 704 a-704 d of second stripe702, respectively.

Note that in further embodiments, the stripe reference generated in step504 may have other forms. For example, in an embodiment, the stripereference may include a vector that includes a storage device identifierand a page slot indicator pair for each of the M data pages. Such anembodiment may be useful when data pages are stored in non-sequentialstorage devices. For example, instead of storing first-fourth data pages704 a-704 d of second stripe 702 in page slots 404 b, 406 b, 408 a, and410 a of storage devices 402 a-402 d, respectively, first-fourth datapages 704 a-704 d may be stored in a non-sequential string of storagedevices, such as being stored in page slots 404 b, 406 b, 410 a, and 412a of storage devices 402 a, 402 b, 402 d, and 402 e, respectively. Insuch case, a stripe reference generated for second stripe 702 may be avector of [(1, 2), (2, 2), (4, 1), (5, 1)], identifying page slots 404b, 406 b, 410 a, and 412 a as storing pages 704 a-704 d of second stripe702, respectively.

The reference that is generated for first stripe 604 may be returned(e.g., transmitted from data store 400) to the device (e.g., one ofcomputers 102 in FIG. 1) performing a store operation at data store 400,after the store operation is completed. Similarly, the reference that isgenerated for second stripe 702 may be returned to the device performinga store operation for second stripe 702 at data store 400, after thestore operation is completed. The references may be later used bydevices (e.g., one of computers 102 in FIG. 1) to access first andsecond data stripes 604 and 702 in data store 602.

Thus, in an example, the device may perform a flowchart 800 shown inFIG. 8. In step 802, a request is transmitted to store data thatincludes M data pages as a stripe in a stripeset of a data store. Forexample, referring to FIG. 1, computer 102 a may transmit a storerequest (e.g., an append operation) through network 104 to data store400 (FIG. 4) to store first stripe 604 in data store 400. In step 804, areference generated for the stripe is received that includes anidentifier for a storage device in which a first data page of the M datapages is stored and a vector that includes a page slot indicator foreach of the M data pages. For example, referring to FIG. 1, computer 102a may receive a response from data store 400 indicating that firststripe 604 was stored in data store 400, including the stripe referenceof an identifier of “1” for storage device 402 a, and a vector of [1,1], identifying page slots 404 a and 404 b that store pages 606 a and606 b of first stripe 604. In a similar fashion, computer 102 a (orother computer 102) may transmit a store request to data store 400, andreceive a response from data store 400 regarding second stripe 702,according to flowchart 800.

FIG. 9 shows a block diagram of a computer 900, according to an exampleembodiment. Computers 102 shown in FIG. 1 may be implemented as computer900, in an embodiment. In an embodiment, flowchart 800 may be performedby computer 900. As shown in FIG. 9, computer 900 may include a datastripe storage interface module 902. Data stripe storage interfacemodule 902 may be configured to generate a storage request 904 (e.g., a“store-stripe” operation), which is transmitted from computer 900 (e.g.,according to step 802) by a network interface of computer 900 to datastore 400. For example, an application executing at computer 900 maydesired to store data at data store 400. Data stripe storage interfacemodule 902 may receive data from the application, and generate storagerequest 904 to store the data at data store 400. In an embodiment,storage request 904 includes the data in the form of a data stripe, suchas one of data stripes 604 and 702 shown in FIG. 7 for storage in datastore 400. In an embodiment, storage request 904 is transmitted to astorage controller at data store 400, which transmits each data page ofthe data stripe to the corresponding storage devices 402 of data store400. In another embodiment, storage request 904 includes a plurality ofstorage request signals, with each storage request signal including acorresponding data page of the data stripe. Each storage request signalis transmitted to a corresponding storage device 402 of data store 400,to store the data page in the corresponding storage device 402, so thatthe data stripe is stored in data store 400.

In an embodiment, prior to transmitting storage request 904, computer900 may transmit a “get-stripeset” request to data store 400. Inresponse to the “get-stripeset” request, computer 900 may receive astripeset reference, which identifies a set of storage devices 402 ofdata store 400 forming a current stripeset where the data stripe may bestored. Storage request 904 may be directed to the set of storagedevices identified by the “get-stripeset” request.

Furthermore, in response to storage request 904, data stripe storageinterface module 902 may receive a storage response 906 from data store400. Storage response 906 may include a stripe reference, such as astripe reference for one of data stripes 604 and 702, generated by datastore 400. In an embodiment, storage response 906 may be received from astorage controller at data store 400. In another embodiment, storageresponse 906 may include a plurality of storage response signals, witheach storage response signal being received from a corresponding storagedevice 402, and indicating a page slot of the storage device 402 inwhich the corresponding data page of the data stripe was stored.

If computer 900 desires to access the data of the data stripe stored indata store 400, computer 900 may transmit a “get-stripe” request to datastore 400. The “get-stripe” request may be directed to a storagecontroller of data store 400, when present, or directly to storagedevices 402 a-402 z (e.g., in a plurality of “get-stripe” or“get-data-page request signals”). The “get-stripe” request includes astripe reference for the data stripe. Data store 400 receives the stripereference as input and returns the data in the stripe identified by thatstripe reference.

Thus, in an embodiment, a technique for storing data stripes of variablesizes is provided. A data stripe that includes M data pages, which maybe the same length or less than the rank of the stripeset, is stored ina data store. Each data page of the data stripe is stored in a firstopen slot of a corresponding storage device of the stripeset, which maybe all or a subset of the N storage devices of the stripeset, dependingon whether the data stripe is the same length or less than the rank ofthe stripeset. A reference to the data stripe is generated, which mayinclude a storage device ID of the first storage device that stores apage of the data stripe, and an array of M addresses that identify thepage slots where each page of the stripe is stored.

As described above, the data stripe may be stored in any combination ofstorage devices of the stripeset, when N>M. In an embodiment, the datastripe may be stored in a “prefix” of the stripeset, which is a“logical” first set of storage devices of the stripeset (e.g., a set ofthe left-most storage devices of stripeset 602 shown in FIG. 7). Forinstance, as described above, the N storage devices of the stripeset maybe associated in a logical sequence, the logical sequence including afirst storage device of the N storage devices at a logical first end ofthe stripeset (e.g., having a storage device identified as the firststorage device of the stripeset, such as by being assigned identifier“1”, etc.) and a second storage device of the N storage devices at alogical second end of the stripeset (e.g., being identified as a laststorage device of the stripeset, such as by having a highest/lastassigned identifier). For example, referring to stripeset 602 shown inFIG. 7, first storage device 402 a may be the storage device at thelogical first end of stripeset 602 (e.g., having the lowest identifierof “1”), and fourth storage device 402 d may be the storage device atthe logical second end of stripeset 602 (e.g., having the highestidentifier of “4”).

Thus, in an embodiment, step 502 of flowchart 500 may be performedaccording to a flowchart 1000 shown in FIG. 10. In step 1002 offlowchart 1000, the first data page of the M data pages of the datastripe is stored in the first storage device. In step 1004, eachsubsequent data page of the M data pages is stored in a correspondingnext consecutive storage device in the logical sequence from the firststorage device. For instance, referring to data stripe 702 shown in FIG.7, first data page 704 a is stored in first storage device 402 a (at alogical first end of stripeset 602), second data page 704 b is stored innext consecutive second storage device 402 b, third data page 704 c isstored in next consecutive third storage device 402 c, and fourth datapage 704 d is stored in next consecutive fourth storage device 402 d (ata logical second end of stripeset 602).

B. Example Embodiments for Sliding Window Striping

After a number of data stripes is stored in a stripeset of a data store,one or more of the storage devices of the stripeset may become full. Insuch case, according to conventional techniques, a new stripeset may beformed in the data store that does not include any of storage devices ofthe previous stripeset, even if one or more of the storage devices ofthe previous stripeset are not full. This is an inefficient use ofstorage.

In an embodiment, as described above, data stripes may be stored in aprefix of a stripeset. If data stripes stored in the stripeset havevarying numbers of data pages, the logical first storage device of thestripeset becomes full before other storage devices of the stripeset. Insuch case, in an embodiment, the stripeset is “advanced,” “slid,” or“shifted.” Sliding the stripeset moves the stripeset in a logicaldirection (e.g., logical left or right) to remove the full storagedevice from the stripeset and to add a non-full storage devices to thestripeset.

For instance, FIG. 11 shows a flowchart 1100 providing a process forstripeset sliding, according to an example embodiment. Flowchart 1100may be performed if a logical end most storage device of a stripesetbecomes full (or otherwise is desired to no longer be included in thestripeset). In an embodiment, flowchart 1100 may be performed by datastore 400 (e.g., by a storage controller of data store 400) shown inFIG. 4. Other structural and operational embodiments will be apparent topersons skilled in the relevant art(s) based on the discussion regardingflowchart 1100. Flowchart 1100 is described as follows.

As shown in FIG. 11, flowchart 1100 begins with step 1102. In step 1102,the first storage device is determined to be full. For example, FIG. 12shows a block diagram of data store 400 including first stripeset 602.As shown in FIG. 12, first stripeset 602 includes first-fourth storagedevices 402 a-402 d (N=4). Storage devices 402 a-402 d are associated ina logical sequence, with storage device 402 a at a logical first end ofstripeset 602 and storage device 402 d at a logical second end ofstripeset 602. According to step 1102, storage device 402 a may bedetermined to be full. As indicated in FIG. 12, page slots 404 a-404 yare full (e.g., storing data pages of data stripes). For instance, whenstorage device 402 a becomes full, storage device 402 a may transmit afull indication to a storage controller of data store 400.Alternatively, storage device 402 a may provide the full indication whena storage request is received by storage device 402 a from the storagecontroller or by another device (e.g., computer 900 shown in FIG. 9).

Note that in the example of FIG. 12, page slots 406 a-406 c of storagedevice 402 b, page slots 408 a and 408 b of storage device 402 c, andpage slots 410 a and 410 b of storage device 402 d are also full, butnot all page slots of storage devices 402 b-402 d are full, so storagedevices 402 b-402 d are not determined to be full in step 1102. However,additional storage devices of stripeset 602 may become fullsimultaneously with storage device 402 a. For example, storage device402 b, and possibly additional storage devices, may become fullsimultaneously with storage device 402 a if a data page is stored instorage device 402 b (and potentially further storage devices) each timea data page is stored in storage device 402 a, and storage device 402 bhas the same storage capacity as storage device 402 a. Note that if datastripes are stored in a prefix of stripeset 602, storage devices ofstripeset 602 that are closest to storage device 402 a will tend tobecome full most rapidly. Because storage device 402 a is at a logicalfirst end of stripeset 602, and thus stores a data page from each datastripe stored in stripeset 602 (assuming data stripes are added to aprefix of stripeset), storage device 402 a is a first storage device ofstripeset 602 to become full.

In step 1104, the first storage device is removed from the stripeset. Inan embodiment, as a result of the full indication, storage device 402 amay be removed from stripeset 602. If further storage devices ofstripeset 602 were also determined to be full in step 1102, thosestorage devices may also be removed from stripeset 602 in step 1104.

In step 1106, a next storage device of the data store is added to thestripeset to be logically positioned at the logical second end of thestripeset adjacent to the second storage device. Referring to FIG. 12,in an embodiment, a next storage device 402 of data store 400 that isnot included in stripeset 602 may be added to stripeset 602 to replacethe removed storage device 402 a. In an embodiment, the storage devicethat is added to stripeset 602 is a storage device 402 of data store 400that is logically next to storage device 402 d at the logical second endof stripeset 602. In the example of FIG. 12, the storage devicelogically positioned next to storage device 402 d is storage device 402e (e.g., storage device 402 e has an identifier of “5” logically next tothe identifier of “4” for storage device 402 d). If further storagedevices of stripeset 602 were removed from stripeset 602 in step 1104,corresponding further storage devices of data store 400 in logicalsequence from storage device 402 e may be added to stripeset 602.

For instance, as shown in FIG. 12, a second stripeset 1202 is formed asan updated version of stripeset 602. Second stripeset 1202 includesstorage devices 402 b-402 e. Storage device 402 a, which was determinedto be full, is not present in second stripeset 1202. Storage device 402e, which is next in logical sequence to storage device 402 d is added tosecond stripeset 1202.

Thus, in an embodiment, a technique for sliding window striping isprovided. The overflow of one or more storage devices at the beginningof a stripeset is handled by assigning to the stripeset a same number ofstorage devices at the end of the stripeset.

C. Example Stripeset Detection Embodiments

Devices that desire to store data stripes may need to know the locationof one or more current, non-empty stripesets in storage in which tostore the data stripes, similarly to the “get-stripeset” requestdescribed above. For example, computer 900 shown in FIG. 9 may desirethe capability to track the store state of storage devices 402 in datastore 400, including the capability to determine at a boot time forcomputer 900 one or more non-empty stripesets in data store 400 wheredata can be stored.

In an embodiment, a storage device may have three states: empty, active,or full. The empty state indicates that the storage device does notstore data. The active state indicates that the storage device stores atleast some data and/or is currently included in a stripeset. The fullstate indicates that the storage device is full (e.g., the portion ofthe storage media of the storage device allocated for storing data pagesof data stripes is filled). In the full state, the storage device cannotprocess further append operations.

In embodiments, each storage device 402 of data store 400 may beconfigured to be self-describing with regard to the state of itsstorage. For example, in an embodiment, each storage device may store astate variable, having a value that indicates a “class” of the storagedevice. For instance, FIG. 13 shows a block diagram of a storage device402, according to an example embodiment. As shown in FIG. 13, storagedevice 402 includes a storage controller 1304, and stores a classvariable 1302. Storage controller 1304 is configured to generate andmaintain class variable 1302. Class variable 1302 may have an integer ornon-integer value that indicates a class, or store state, of storagedevice 402. For example, class variable 1302 may have a value of zero(or other value) to indicate an empty state for storage device 402, avalue of one (or other value) to indicate an active state for storagedevice 402, or a value of two (or other value) to indicate a full statefor storage device 402. Each of storage devices 402 a-402 z of FIG. 4may include a respective storage controller 1304 and store a respectiveclass variable 1302. In an embodiment, class variable 1302 may be storedpersistently (e.g., in non-volatile storage), so that if storage device402 fails and subsequently recovers, storage device 402 retains the sameclass indicated by class variable 1302 at the time of the failure. Classvariable 1302 may be stored in various locations, including storingclass variable 1302 in memory allocated to or included in storagecontroller 1304, storing class variable 1302 in each data page stored instorage device 402 (e.g., in a header for the data page), or storingclass variable 1302 at another location.

In an embodiment, the class variable of a storage device may be aparameter to an append operation performed with respect to the storagedevice. For example, if computer 900 of FIG. 9 is attempting to store adata stripe in data store 400 of FIG. 4, data stripe storage interfacemodule 902 may include a class indication in store request 904transmitted to data store 400. The class indication included in storerequest 904 may be compared by each storage controller 1304 of thestorage devices of the current stripeset with the corresponding classvariable 1302 to determine how storage request 904 is processed, and maycause class variable 1302 of one or more of the storage devices 402 ofthe current stripeset to be modified.

For example, FIG. 14 shows a flowchart 1400 providing a process forhandling storage in a storage device, according to an exampleembodiment. Flowchart 1400 may be performed by one or more storagedevices 402 of data store 400. Other structural and operationalembodiments will be apparent to persons skilled in the relevant art(s)based on the discussion regarding flowchart 1400. Flowchart 1400 isdescribed as follows.

As shown in FIG. 14, flowchart 1400 begins with step 1402. In step 1402,a class variable is associated with a corresponding storage device of adata store. As described above, as shown in FIG. 13, class variable 1302may be associated with storage device 402. Each storage device 402 of astripeset may have an associated class variable 1302. Class variable1302 indicates a class or store status of the corresponding storagedevice 402.

In step 1404, the class variable is enabled to be modified by a computerthat stores a data page of a data stripe in the corresponding storagedevice. For example, computer 900 may transmit storage request 904 (FIG.9) to store a data stripe in stripeset 602 shown in FIG. 6. A data pageof the data stripe may be stored in storage device 402 shown in FIG. 13.As a result of storing the data page in storage device 402, a value ofclass variable 1302 may be modified. For example, if storing the datapage in storage device 402 causes storage device 402 to become full,class variable 1302 may be modified by storage controller 1304 from anactive state to a full state.

In step 1406, the class variable is enabled to be reset by a computerthat erases data stored in the corresponding storage device. Forexample, computer 900 may transmit an erase request to storage device402 of FIG. 9 (and optionally to further storage devices). As a result,a value of class variable 1302 may be reset by storage controller 1304(e.g., changed to a “0” value or otherwise modified) to indicate thatstorage device 402 is in an empty state. In an embodiment, an eraseoperation may be the only operation that can decrease the value of classvariable 1302, although in other embodiments, other operations may beable to decrease the value of class variable 1302. In an embodiment, anerase operation may be configured to clear a portion of the page slotsof a storage device. In such case, class variable 1302 may be reset tozero when all page slots of the storage device have been erased.

Step 1404 may be performed in various ways. For example, FIG. 15 shows aflowchart 1500 providing a process for modifying a class variable basedon a store request, according to an example embodiment. Flowchart 1500may be performed by storage controller 1304 of FIG. 13, for example. Forinstance, FIG. 16 shows a block diagram of storage controller 1304,according to an example embodiment. As shown in FIG. 16, storagecontroller 1304 includes a class comparator 1602. Further structural andoperational embodiments will be apparent to persons skilled in therelevant art(s) based on the discussion regarding flowchart 1500.Flowchart 1500 is described as follows.

As shown in FIG. 15, flowchart 1500 begins with step 1502. In step 1502,a request is received from the computer to store the data page in thestorage device, the request including a class indication. For example,as described above, storage request 904 shown in FIG. 9 may be receivedby a storage device, such as storage device 402 shown in FIG. 13.Storage request 904 may provide a data page to be stored in storagedevice 402, and may include a class indication, shown as a classindication 1604 in FIG. 16.

In step 1504, the data page is enabled to be stored in a next availablepage slot of the storage device if the class indication has a firstrelationship with the class variable. In embodiments, the firstrelationship between the class indication 1604 and class variable 1302associated with class variable 1302 to enable the data page to be storedmay be defined in any manner, such as class indication 1604 and classvariable 1302 being equal. In an embodiment, class comparator 1602 shownin FIG. 16 may be configured to compare class indication 1604 receivedin storage request 904 with class variable 1302 of storage device 402 todetermine a relationship 1606. In an embodiment, if relationship 1606 isdetermined as equal, an append operation may be performed as normal,such that a data page provided in storage request 904 is stored in apage slot of storage device 402.

In step 1506, the data page is enabled to be stored in a next availablepage slot of the storage device and the class variable is modified ifthe class indication has a second relationship with the class variable.In embodiments, the second relationship between the class indicationreceived in storage request 904 and class variable 1302 associated withclass variable 1302 to enable the data page to be stored and the classvariable to be modified may be defined in any manner, such as classvariable 1302 being less than class indication 1604. For example, ifrelationship 1606 determined by class comparator 1602 indicates thatclass variable 1302 is less than class indication 1604, storagecontroller 1304 may increase class variable 1302 to the value of classindication 1604. The append operation may also be performed, such that adata page provided in storage request 904 is stored in a page slot ofstorage device 402.

In step 1508, a response to the request is generated that includes theclass variable if the class indication has a third relationship with theclass variable. In embodiments, the third relationship between the classindication received in storage request 904 and class variable 1302associated with class variable 1302 may be defined in any manner,including class variable 1302 being greater than class indication 1604.For example, if relationship 1606 determined by class comparator 1602indicates that class variable 1302 is greater than class indication1604, the append operation is not performed. Instead, storage device 402may transmit an exception message to computer 900 that includes thecurrent value of class variable 1302 of storage device 402.

Note that in an embodiment, a get-class operation may be configured toenable a device to request the value of class variable 1302 of a storagedevice 402. For example, computer 900 may transmit a get-class requestto a storage device 402. In an embodiment, a get-class operation may beincluded in another operation, such as a read operation, which transmitsa page slot address to a storage device, and the data stored in the pageslot address is received in response. The read operation may also returna value of the class variable of the storage device.

Modifying the behavior of an append operation according to a classvariable, as described above, may be used to enable multiple computersto share a set of storage devices without additional synchronization. Inan embodiment, after a device (e.g., computer 900) increases the valueof the class variable of a storage device by performing an appendoperation, subsequent append operations have to use the increased classvalue or a higher class value to be enabled to be performed. This isaccomplished by communications between computer 900 and the storagedevices, and does not require computer-to-computer communication. Ifcomputer 900 attempts an append operation using a class indication withlower value than the class variable of the storage device, the appendoperation is rejected, and the value of the class variable of thestorage device is transmitted to computer 900 in the exception messagein response.

In an embodiment, if the class indication received in step 1502 (FIG.15) from computer 900 indicates an active class, the store-stripeoperation stores a data page in storage device 402 (assuming the classvariable of the storage device is equal to the class indication).Computer 900 may “seal off” a stripeset by appending data pages to thestorage devices with a “full” class value provided for the classindication. As indicated in step 1506, the class variable of the storagedevice may be increased to the value of class indicator (in this case, a“full” class value) if computer 900 provides a class indicator with ahigher value than the class variable of the storage device. The “full”class value prevents any further append operations to the storage deviceusing an active class as class indication. In an embodiment, the storagedevice may be configured to automatically increase its class variablefrom an “active” value to a “full” value when there is an attempt toexecute an append operation, but the storage device does not havestorage space for a data page.

In an embodiment, a computer, such as computer 900, may be configured todetermine an active stripeset in a data store, such as data store 400 inFIG. 4. For example, computer 900 may be configured to scan the sequenceof storage devices 402 a-402 y of data store 400 to find a subsequenceof storage devices 402 a-402 y that have class variables indicating anactive state.

In another embodiment, data store 400 may be log-structured, such thatstorage devices are filled up with data pages in a logical sequence. Forexample, referring to FIG. 12, as described above, storage devices atthe logical first end (e.g., storage device 402 a) of data store 400 maybecome full before storage devices closer to the logical second end(e.g., storage device 402 z) of data store 400. In the example of FIG.12, this may mean that storage devices 402 a-402 z sequentially becomefull from left to right (e.g., where storage devices 402 toward the lefthave logically lower numbered identifiers than storage devices 402toward the right in FIG. 12). After one or more of storage devices 402a-402 z are full, a “garbage collector” may be enabled to empty the fullstorage devices 402 having logically lower numbered identifiers, so theycan subsequently be erased.

For instance, FIG. 17 shows a block diagram of a data store 1700,according to an example embodiment. Data store 1700 is similar to datastore 400 shown in FIG. 12, with the addition of a storage cleaningmodule 1702. Storage cleaning module 1702 is configured to perform a“garbage collector” function. Storage cleaning module 1702 is configuredto clean out data from full storage devices, so that the storage devicesmay again be used in a stripeset to store data pages of data stripes.For example, referring to FIG. 17, storage devices 402 a and 402 b areboth full, because page slots 404 a-404 y of storage device 402 a andpage slots 406 a-406 y each store a data page. Storage cleaning module1702 may determine that storage device 402 a is to be cleaned. In suchcase, storage cleaning module 1702 is configured to save each stripestored in data store 1700 that includes a data page stored in storagedevice 402 a by copying the stripe to a currently active stripeset. Forexample, page slot 404 a of storage device 402 a may store a data pageincluded in a three-data page data stripe stored in storage devices 402a-402 c. Storage cleaning module 1702 may copy the three-data page datastripe from storage devices 402 a-402 c to an active stripeset (e.g., instorage devices 402 d-402 f). In this manner, page slot 404 a of storagedevice 402 a is cleaned. Each page slot 404 of storage device 402 a maybe cleaned in a similar manner, and/or one or more page slots 404determined to store data pages of unneeded data stripes can be erased bystorage cleaning module 1702. Storage cleaning module 1702 may determinewhich stripes are needed (and may save them, as described above) orunneeded in any manner. After storage cleaning module 1702 copies all ofthe useful data stripes having data pages stored in storage device 402 ato different storage devices, storage device 402 a may be erased andmade available to be included in a subsequent stripeset for storingsubsequent data stripes. Because storage devices 402 at a logical firstend of data store 1700 tend to become full first, storage cleaningmodule 1702 may operate to clean storage devices 402 a-402 z in asequential fashion from the logical first end of data store 1700 to thelogical second end of data store 1700 (e.g., from left to right in FIG.17), after each successive storage device becomes full.

In such log-structured storage, storage devices 402 of data store 400can be configured in a “ring” configuration. For example, as describedabove, storage devices 402 a-402 z may be associated in a logicalsequence, from storage device 402 a to storage device 402 z (e.g.,having storage device identifiers 1-N, respectively), where storagedevice 402 b logically follows storage device 402 a, storage device 402c follows storage device 402 b, etc. Furthermore, the next storagedevice in the logical sequence following the Nth storage device, whichis storage device 402 z in FIG. 17, is the first storage device, whichis storage device 402 a in FIG. 17.

At any given time, a data store configured in a ring configuration mayhave three subsequences: a contiguous sequence of empty storage devices,followed by a contiguous sequence of full storage devices, followed by acontiguous sequence of active storage devices. For example, referring toFIG. 17, data store 1700 includes a contiguous sequence of empty storagedevices, storage devices 402 e-402 z, followed by a contiguous sequenceof full storage devices, storage devices 402 a and 402 b, followed by acontiguous sequence of active storage devices, storage devices 402 c and402 d. A sequence of full storage devices may not be present when thedata store 1700 is initiated or if storage cleaning module 1702 hascleared all full storage devices. The sequence of active storage devicesmay not be present when data store 1700 is initiated, or immediatelyafter filling a previously active stripeset and before starting a nextstripeset. When data store 1700 is initiated, no active or full storagedevices may be present because all storage devices are empty. However,much of the time, all three sequences are present.

As described above, a computer, such as computer 900, may determine acurrently active stripeset by a form of binary search, where a range ofstorage devices containing active storage devices is determined. Acorner case may arise when both a prefix and a suffix of the storagedevices of the data store are erased. In such case, the data store mayinclude two sequences of erased storage devices (e.g., may include afirst sequence of erased storage devices, followed by full storagedevices, followed by active storage devices, followed by a secondsequence erased storage devices). If a middle storage device in the datastore is also erased, then a first step of a binary search doesn'treduce the number of storage devices to be searched. If the range offull and active storage devices is relatively small, this problem canrepeat and may ultimately defeat the logarithmic search time that abinary search normally offers.

In an embodiment, to avoid the corner case, and enable search time to belogarithmic in the number of storage devices, a persistent updatableepoch number may be assigned to each storage device. For instance, FIG.18 shows a block diagram of a storage device 402, according to anexample embodiment. As shown in FIG. 18, storage device 402 includes astorage controller 1802. Storage controller 1802 is configured togenerate class variable 1302 (in a similar fashion as described abovewith respect to storage controller 1304 in FIG. 13) and to generate anepoch value 1804. Epoch value 1804 is a number or other representationassigned to storage device 402 configured to indicate an erase state ofstorage device 402 relative to other storage devices in a data store.Each storage device 402 in a data store (e.g., data store 400, datastore 1700, etc.) may include a storage controller 1802 to generate acorresponding epoch value 1804. When the data store containing storagedevice 402 is initialized, storage controller 1802 sets epoch value 1804to an initial value. Each time that storage device 402 is erased,storage controller 1802 increments epoch value 1804 (e.g., increasesepoch value 1804 by one). Thus, if both a prefix and a suffix of thestorage devices of the data store are erased/empty, they will eachinclude the same value for epoch value 1804 only when the data store isfirst initialized. At later times, the first sequence of erased storagedevices of the data store will have a higher value for epoch value 1804than the second sequence of erased storage devices of the data store.

FIG. 19 shows a flowchart 1900 providing a process for determining anactive stripeset, according to an example embodiment. Flowchart 1900 maybe performed by a device (e.g., a computer 102 in FIG. 1) with regard toa data store that includes storage devices having epoch values, asdescribed above. For instance, FIG. 20 shows a block diagram of acomputer 2000, according to an example embodiment. In an embodiment,computer 2000 may perform flowchart 1900. As shown in FIG. 20, computer2000 includes data stripe storage interface module 902 (as describedabove with respect to FIG. 9) and a stripeset determiner module 2002.Stripeset determiner module 2002 is configured to determine an activestripeset in a data store. Further structural and operationalembodiments will be apparent to persons skilled in the relevant art(s)based on the discussion regarding flowchart 1900. Flowchart 1900 isdescribed as follows.

As shown in FIG. 19, flowchart 1900 begins with step 1902. In step 1902,a logically closest non-empty storage device of the plurality of storagedevices to the logical first end is determined. For example, in anembodiment, stripeset determiner module 2002 may perform a search of adata store for a logically closest non-empty storage device of the datastore to the logical first end of the data store.

In step 1904, an active storage device of the plurality of storagedevices in a range of the logical sequence from the logically closestnon-empty storage device to the second storage device is determined. Forexample, in an embodiment, stripeset determiner module 2002 may performa search of the data store for an active storage device (e.g., an activestorage device having an active value for class variable 1302), in arange of storage devices of the data store from the logically closestnon-empty storage device of the data store to the logical second end ofthe data store.

In step 1906, a continuous range of active storage devices in theplurality of storage devices that includes the determined active storagedevice is determined. For example, in an embodiment, stripesetdeterminer module 2002 may perform a search of the data store for acontinuous range of active devices in the data store that include theactive storage device determined in step 1904. The determined continuousrange of active storage devices is the determined stripeset.

Stripeset determiner module 2002 may be configured to perform flowchart1900 in various ways. In an embodiment, flowchart 1900 may be performedas a series of operations executed by stripeset determiner module 2002.For example, flowchart 1900 may be performed by stripeset determinermodule 2002 as a “GetActiveStripeset” operation, which results in arange of storage devices that comprise an active stripeset beingreturned from the data store being analyzed. Step 1902 may be performedby stripeset determiner module 2002 as a “GetFirstNonEmpty” operationconfigured to return the first non-empty storage device as a parameter“F”. Step 1904 may be performed by stripeset determiner module 2002 as a“GetActiveFromRange(F, S)” operation that uses the parameter “F” and aparameter “S” that is the last storage device in the data store, toreturn the active storage device as a parameter “AS.” Step 1906 may beperformed by stripeset determiner module 2002 as a“GetStripesetFromActive(AS)” operation that uses the parameter “AS” toreturn the continuous range of active storage devices of the data storeas the active stripeset.

FIG. 21 shows a block diagram of stripeset determiner module 2002,according to an example embodiment. Stripeset determiner module 2002 ofFIG. 21 is configured to perform the steps of flowchart 1900, asdescribed above. As shown in FIG. 21, stripeset determiner module 2002includes a non-empty storage device determiner module 2102, an activestorage device determiner module 2104, and an active range determinermodule 2106. These elements of stripeset determiner module 2002 aredescribed as follows.

In an embodiment, non-empty storage device determiner module 2102 may beconfigured to perform step 1902 of flowchart 1900. For example, in anembodiment, non-empty storage device determiner module 2102 may performstep 1902 according to a flowchart 2200 shown in FIG. 22. Flowchart 2200is described as follows.

In step 2202, the first storage device is indicated to be the logicallyclosest non-empty storage device if the first storage device isnon-empty. In an embodiment, non-empty storage device determiner module2102 is configured to determine whether the logically first storagedevice of the data store is non-empty, and if so, to indicate thelogically first storage device to be the closest non-empty storagedevice to the logical first end of the data store. For instance, FIG. 23shows a block diagram of data store 1700 of FIG. 17, according to anexample embodiment. Referring to FIG. 23, storage device 402 a is thelogically first storage device, and is non-empty. Thus, storage device402 a is indicated as the closest non-empty storage device to thelogical first end of data store 1700, according to flowchart 2200.

In step 2204, all of the plurality of storage devices are indicated tobe empty if the first and second storage devices are empty and have asame epoch value. In an embodiment, non-empty storage device determinermodule 2102 is configured to determine whether the logically laststorage device of the data store is empty, and if so, and if thelogically first and last storage devices of the data store have the sameepoch value, to indicate that all storage devices in the data store areempty (i.e., a stripeset is not present).

In step 2206, a binary search is performed over the logical sequencefrom the first storage device to the second storage device to determinea logically closest storage device to the logical first end having anepoch value that is different from an epoch value of the first storagedevice. In an embodiment, non-empty storage device determiner module2102 is configured to perform a binary search over the set of storagedevices to find the first storage device whose epoch number is differentthan that of the first storage device. For example, non-empty storagedevice determiner module 2102 may be configured to perform a recursivefunction, including determining a middle storage device between the endmost storage devices (e.g., middle storage device ID=(the low storagedevice ID+high storage device ID)/2). If the low storage device and themiddle storage device have the same epoch value, a storage devicebetween the middle storage device and the high storage device isdetermined, and their epoch values are compared. Otherwise, if the lowstorage device and the middle device have different epoch values, astorage device between the low storage device and the middle storagedevice is determined, and their epoch values are compared. This processis continued until the storage device closest to the logical first endthat has an epoch value different from that of the first storage deviceis located.

In an embodiment, active storage device determiner module 2104 shown inFIG. 21 may be configured to perform step 1904 of flowchart 1900. Forexample, in an embodiment, active storage device determiner module 2104may perform step 1904 according to a flowchart 2400 shown in FIG. 24.Flowchart 2400 is described as follows.

In step 2402, the logically closest non-empty storage device isindicated to be the active storage device if the logically closestnon-empty storage device is active. In an embodiment, active storagedevice determiner module 2104 is configured to determine whether thelogically first storage device of the data store is active, and if so,to indicate the logically first storage device to be the active storagedevice. For instance, referring to FIG. 23, storage device 402 a wasdetermined to be the logically closest non-empty, but is not active.Thus, storage device 402 a is not indicated as the active storagedevice.

In step 2404, the second storage device is indicated to be the activestorage device if the second storage device is active and the logicallyclosest non-empty storage device is not active. In an embodiment, activestorage device determiner module 2104 is configured to determine whetherthe logically last storage device of the data store is active, and ifso, to indicate the logically last storage device to be the activestorage device. For instance, referring to FIG. 23, storage device 402 zis the logically last storage device, but is not active. Thus, storagedevice 402 z is not indicated as the active storage device.

In step 2406, a binary search is performed over the logical sequencefrom the logically closest non-empty storage device to the secondstorage device to determine an active storage device. For example, in anembodiment, active storage device determiner module 2104 may beconfigured to perform a binary search across the data store to determinean active storage device. For example, active storage device determinermodule 2104 may be configured to perform a recursive function, includingdetermining a middle storage device between the end most storage devices(e.g., middle storage device ID=(the low storage device ID+high storagedevice ID)/2). If the middle storage device is active, the middlestorage device is indicated as the active storage device. If the middlestorage device is empty, a next middle storage device is determinedbetween the current low storage device and the current middle storagedevice, and the next middle storage device is analyzed to determinewhether it is active. If the middle storage device is full, a nextmiddle device is determined between the current middle storage deviceand the current high storage device. This process is continued until anactive storage device is located.

With regard to the example of FIG. 23, a middle storage device betweenstorage devices 402 a and 402 z may be storage device 402 m, which maynot be active, and may be empty. Thus, a next middle storage device isdetermined between storage device 402 a and storage device 402 m, whichmay be storage device 402 g. Storage device 402 g may not be active, andmay be empty. Thus, a next middle storage device is determined betweenstorage device 402 a and storage device 402 g, which may be storagedevice 402 d. Storage device 402 d is active, and thus is indicated asthe active storage device determined for data store 1700 according toflowchart 2400.

In another embodiment, an exponential probing sequence may be used instep 2406 instead of the binary search. Starting from a low storagedevice, storage devices low+1, low+2, low+4, low+8, low+16, etc., areprobed, until either an active storage device is encountered (in whichcase it is returned), or an empty storage device or the last storagedevice is encountered (in which case recursively perform the search onthe range of storage devices defined by the last two probes).

In an embodiment, active range determiner module 2106 shown in FIG. 21may be configured to perform step 1906 of flowchart 1900. For example,in an embodiment, active range determiner module 2106 may perform step1906 according to a flowchart 2500 shown in FIG. 25. Flowchart 2500 isdescribed as follows.

In step 2502, the plurality of storage devices in the logical sequenceis searched from the determined active storage device towards the firststorage device for a first non-active storage device. For example,active range determiner module 2106 is configured to find a firststorage device in the range of active storage devices by searchingsequentially from the determined active storage device towards thelogical first storage device. For example, referring to FIG. 23, storagedevice 402 b is determined to be the first non-active storage devicewhen searching from active storage device 402 d towards storage device402 a.

In step 2504, the plurality of storage devices in the logical sequenceis searched from the determined active storage device towards the secondstorage device for a second non-active storage device. For example,active range determiner module 2106 is configured to find a last storagedevice in the range of active storage devices by searching sequentiallyfrom the determined active storage device towards the logical laststorage device. For example, referring to FIG. 23, storage device 402 fmay be determined to be the second non-active storage device whensearching from active storage device 402 d towards storage device 402 z.

In step 2506, the continuous range of active storage devices isindicated to be a continuous range of storage devices between the firstnon-active storage device and the second non-active storage device. Forexample, referring to FIG. 23, range determiner module 2106 may beconfigured to set the continuous range of active storage devices to bethe continuous range from storage device 402 c to storage device 402 e,which are between storage device 402 b determined in step 2502 andstorage device 402 f determined in step 2504. As indicated in FIG. 23,the continuous range of storage devices from storage device 402 c tostorage device 402 e is an active stripeset 2302.

In another embodiment, storage devices included in a currently activestripeset may be tracked by maintaining a master directory. For example,FIG. 26 shows a block diagram of a data store 2600 that maintains amaster directory 2602 (e.g., in memory/storage) (storage devices 402 ofdata store 2600 are not shown in FIG. 26 for ease of illustration).Master directory 2602 indicates which storage devices are included inone or more currently active stripesets. Whenever there is a change tothe set of storage devices included in an active stripeset, masterdirectory 2602 is updated to indicate the modification. When a device(e.g., computer 900) that accesses storage devices of data store 2600 isinitialized (e.g., boots up), the device may read master directory 2602to determine the bounds of the current stripeset in data store 2600. Inan embodiment, master directory 2602 may be an append-only log, wherechanges to a current stripeset are appended to master directory 2602rather than be written over master directory 2602.

Although master directory 2602 may be used to track a current stripeset,master directory 2602 may become inaccessible due to a storage device ornetworking failure. Thus, in an embodiment, copies of master directory2602 may be stored in multiple locations (e.g., in and/or outside ofdata store 2600). The multiple copies of master directory 2602 may bekept in synch by copying master directory 2602 each time it is modified.Furthermore, updates to master directory 2602 need to be coordinatedbetween the accessing devices (e.g., computers 102 a-102 c in FIG. 1).In contrast, a stripeset may be determined according to flowchart 1900at any time, with the state of the included storage devices typicallybeing available unless one or more of the storage devices areunavailable. Using class information, synchronization is not required.Each accessing device is independently enabled to determine a change ofthe state of a storage device. Moreover, as described above in anembodiment, an accessing device may include a class indicator as aparameter to an append operation, and a receiving storage deviceprocesses the append operation if the class indicator of the appendoperation is greater than or equal to the class of the storage device.

Thus, in an embodiment, a technique for associating a class variablewith each storage device is provided. In an embodiment, a requestingdevice may increment the class variable by appending data in a higherclass to the storage device, and may reset the class variable to zero byerasing the storage device. At boot time, a requesting device maydetermine the stripeset for a class by finding the sequence of storagedevices of an active class. For example, in an embodiment, if the datastore is log-structured, a requesting device can use a binary searchalgorithm to find the stripeset for the class.

D. Example Embodiments for Multiclass Stripesets

Load balancing across storage devices in a data store may be desired dueto the relative frequency of data reads and writes for different typesof data stored in the data store. For example, a database system maymaintain a log that is stored in a stripeset. Most storage operationsperformed with regard to the log may be append operations. Although thelog data may rarely be read after it stored, the log data typically isretained for a relatively long period in case the database system fails,in which case the log is used for recovery. Thus, if a stripeset isconfigured to store only log data, poor utilization of I/O operationsavailable with regard to the log stripeset may result. The stripeset maybe heavily utilized while the log is being written. However, after thestripeset is filled up, the stripeset may be idle most of the time untilits content is garbage collected (e.g., by copying the log to an archivemedium).

In contrast to the log, the database stored in the database system mayhave a relatively low amount of update activity and a relatively largeamount of read activity. Unlike the stripeset that stores the log, astripeset that stores the database may receive a relatively large numberof read operations after it is written. Thus, after the stripeset of thedatabase is full, the stripeset may still be actively used.

Writing multiple types of data to a stripeset at the same time may beundesirable. For instance, it is well known that a log can be abottleneck in a database system, because the transaction rate is limitedby the rate at which data can be appended to the log. Therefore, duringthe time that a stripeset is being used for appending to the log, thestripeset may not be desirable for storing other types of data. Forexample, database updates may undesirable to the stripeset during thesame time that log updates may be received by the stripeset, becausethis would use some of the available update bandwidth of the stripesetand thus reduces the maximum transaction rate.

In an embodiment, multiples types of data may be stored on each storagedevice of a data store in a manner to balance the workload of the datastore. The class mechanism can be used to control the type of data beingwritten to the stripeset by using different classes for different kindsof data. For example, instead of having a single “active” class, therecould be multiple active classes. For instance, when a log and databasedata are stored in a data store, a database class and a log class may bepresent as active classes. In such an embodiment, there may be fourtotal classes or states, such as an empty state, a database state, a logstate, and a full state. Each class may be indicated in class variable1302 (FIG. 13) for a corresponding storage device 402 by a correspondinginteger or other value. For example, class variable 1302 may have avalue of zero to indicate an empty state for storage device 402, a valueof one to indicate a database state for storage device 402, a value of 2to indicate a log state for storage device 402, or a value of three toindicate a full state for storage device 402. When log data is writtento storage device 402, class variable 1302 may be set to indicate thelog state, and when database data is written to storage device 402,class variable 1302 may be set to indicate the database state.

In an embodiment, one or more active stripesets may be present forstoring the log and one or more active stripesets may be present forstoring the database. For example, a stripeset may be initiallydesignated to be used to store database data. When the storage devicesof the stripeset reach a certain fullness threshold, such as being 70%full, the stripeset may be redesignated to be used to store log data.According to the class mechanism, the stripeset may be redesignated fromdatabase data to log data by appending a stripe of the log class to thestripeset. Appending a stripe of the log class to the stripesetincreases the value of class variable 1302 for the storage devices ofthe stripeset, and thereby prevents subsequent append operations fromusing the stripeset for the database class. This technique enablesmulticlass stripesets to be generated, because two or more distinctclasses of data are stored in the same stripeset.

FIG. 27 shows a flowchart 2700 providing a process for generating amulticlass stripeset, according to an example embodiment. Flowchart 2700may be performed by a device storing data in a data store, such ascomputer 900 shown in FIG. 9, or may be performed by one or more storagedevices in the data store. Further structural and operationalembodiments will be apparent to persons skilled in the relevant art(s)based on the discussion regarding flowchart 2700. Flowchart 2700 isdescribed as follows.

As shown in FIG. 27, flowchart 2700 begins with step 2702. In step 2702,at least one data page that includes first data of a first data type isstored in a storage device of the data store when the class variable hasa first value. For example, FIG. 28 shows a block diagram of data store400, according to an example embodiment. As shown in FIG. 27, storagedevices 402 a-402 c form a stripeset 2802 in data store 400. First andsecond data stripes 2804 and 2806 are shown stored in stripeset 2802,for purposes of illustration. For example, data stripes 2804 and 2806may be stored in data store 400 by computer 900 of FIG. 9. Both of firstand second data stripes 2804 and 2806 include data pages of a first datatype (“first data type page”) (e.g., database data) stored in each ofstorage devices 402 a-402 c. In an embodiment, storage devices 402 a-402c each have an associated class variable 1302 having a value associatedwith the first data type when first and second data stripes 2804 and2806 are stored therein.

For example, FIG. 29 shows a block diagram of storage devices 402 a-402c, indicating respective class variables 2902 a-2902 c associated withstorage devices 402 a-402 c. Example values for class variables 2902a-2902 c for storage devices 402 a-402 c are shown below that may bepresent when data stripes 2804 and 2806 are stored in storage devices402 a-402 c:

Class variable 2902 a=1

Class variable 2902 b=1

Class variable 2902 c=1

Thus, in the current example, class variables 2902 a-2902 c each have avalue of “1,” which is representative of the first data type, andindicate data stripes 2804 and 2806 as having a class of the first datatype.

In step 2704, the class variable is changed from the first value to asecond value representative of a second data type. For instance, examplechanged values for class variables 2902 a-2902 c for storage devices 402a-402 c are shown below:

Class variable 2902 a=2

Class variable 2902 b=2

Class variable 2902 c=2

In this example, a value of “2” is representative of a second data typefor data that may be stored in storage devices 402 a-402 c. Classvariables 2902 a-2902 c associated with storage devices 402 a-402 c maybe changed from the value of “1” to the value of “2” in various ways.For example, storage devices 402 a-402 c may each determine that theyhave reached a predetermined level of fullness (e.g., 50% or otherpredetermined level of filled storage medium, predetermined number offilled data pages, etc.). Storage controllers 1304 (FIG. 13) of each ofstorage devices 402 a-402 c may be configured to increment (or otherwisechange/modify) their respective class variable 2902 a-2902 c when thepredetermined level of fullness is reached.

In an embodiment, computer 900 (or other computer providing data tostore in storage devices 402 a-402 c) may transmit a class indicationwith corresponding data to storage devices 402 a-402 c. The classindication may indicate the class of the corresponding data, and storagecontrollers 1304 of each of storage devices 402 a-402 c may beconfigured to change their class variables 2902 a-2902 c to match thereceived class indication. Alternatively, computer 900 may transmit aninstruction to storage devices 402 a-402 c to increment (or otherwisemodify) class variables 2902 a-2902 c.

In step 2706, at least one data page that includes second data of thesecond data type is stored in the storage device of the data store. Forexample, as shown in FIG. 28, a third data stripe 2808 may be stored instripeset 2802 by computer 900 of FIG. 9. Third data stripe 2808includes data pages of the second data type (“second data type page”)(e.g., log data) stored in each of storage devices 402 a-402 c. Becauseclass variables 2902 a-2902 c associated with storage devices 402 a-402c have a value associated with the second data type when third datastripe 2808 is stored therein, third data stripe 2808 is stored ashaving a class of the second data type.

As such, stripeset 2802 of data store 400 stores two classes of datastripes—first and second data stripes 2804 and 2806 having a classassociated with the first data type, and third data stripe 2808 having aclass associated with the second data type. As such, stripeset 2802 is amulticlass stripeset. In embodiments, further classes of data stripesmay be stored in stripeset 2802, as desired. Although we have describedtwo data types, such as database data and log data, there are caseswhere it is desirable to segregate other types of data updates intoseparate classes. For example, it may be desirable to separate classesfor small database records, large database records (such as large binaryobjects also known as BLOBs), garbage collected data, and/or differenttypes of logs. A different class variable value may be associated witheach type of data update.

Thus, embodiments are provided for storing multiple classes of data in astripeset, where each class is represented by a class variable value(e.g., an integer). A device desiring to store data may be enabled toincrement (or otherwise modify) the class variable of a stripeset byappending data in a different (e.g., a higher) class. The class of astripeset may change when the associated storage devices reach apredefined fullness threshold, or for other reason.

E. Example Combination Embodiments

The embodiments described herein may be combined in any manner. Forexample, in an embodiment, sliding window stripesets and multiclassstripesets can be combined, such as by arranging stripesets of adjacentclasses in adjacent groups of storage devices in decreasing order ofclass. For instance, FIG. 30 shows a block diagram of data store 400including multiple stripesets that can slide and can overlap to formmulticlass stripesets, according to an example embodiment. As shown inFIG. 30, a first stripeset 3002 includes storage devices 402 a-402 c anda second stripeset 3004 includes storage devices 402 d and 402 e. Firststripeset 3002 stores a first data stripe 3006 (data pages 3010 a-3010 cstored in page slots 404 y, 406 b, and 408 b) and second stripeset 3004stores a second data stripe 3008 (data pages 3012 a and 3012 b stored inpage slots 410 a and 412 a). In the current example, first stripeset3002 is associated with a first data class and second stripeset 3004 isassociated with a second data class. As such, class variables associatedwith storage devices 402 a-402 e in FIG. 30 may be as indicated below inTable 1:

TABLE 1 storage storage storage storage storage device device devicedevice device 402a 402b 402c 402d 402e Class Variable: 2 2 2 1 1In Table 1, the class variable value of 2 is associated with the firstdata class stored in first stripeset 3002, and the class variable valueof 1 is associated with the second data class stored in second stripeset3004.

Data stripes may be stored in first and second stripesets 3002 and 3004in various ways, and overflow of storage devices 402 a-402 e may behandled in various ways. For instance, FIG. 31 shows a flowchart 3100providing a process for storing a data stripe, according to an exampleembodiment. Flowchart 3100 may be performed by a device storing data ina data store, such as computer 900 shown in FIG. 9, and/or may beperformed by one or more storage devices in the data store. Furtherstructural and operational embodiments will be apparent to personsskilled in the relevant art(s) based on the discussion regardingflowchart 3100. Flowchart 3100 is described as follows.

As shown in FIG. 31, flowchart 3100 begins with step 3102. In step 3102,a first set of data pages is provided to be stored in a first stripesetof a data store. For instance, computer 900 (FIG. 9) may provide a thirddata stripe that includes a set of data pages to be stored in firststripeset 3002.

In step 3104, the first storage device is determined to be full. Forexample, in an embodiment, storage device 402 a may determine thatstorage device 402 a is full, as indicated in FIG. 30, where each ofpage slots 404 a-404 y store a respective data page.

In step 3106, the first storage device is removed from the firststripeset. For example, in an embodiment, because storage device 402 awas determined to be full in step 3104, storage device 402 a is removedfrom first stripeset 3002. The class variable associated with storagedevice 402 a may be incremented (or otherwise modified) to a value(e.g., “3”) that indicates a full state for storage device 402 a.

In step 3108, a third storage device of the data store is added to thefirst stripeset, the third storage device of the data store having anassociated class variable that indicates a class of a second stripesetof the data store. For example, as shown in FIG. 30, it may be desiredto add the next consecutive storage device 402 to first stripeset 3002in the logical sequence of storage devices 402 a-402 y, which is storagedevice 402 d. FIG. 30 indicates storage device 402 d as included insecond stripeset 3004, and has a class variable indicated in Table 1above representative of second stripeset 3004. According to step 3108,storage device 402 d is added to first stripeset 3002.

In step 3110, the class variable is changed to indicate a class of thefirst stripeset. For example, the class variable of storage device 402d, which previously indicated the class of second stripeset 3004, may beincremented (or otherwise modified) to indicate the class of firststripeset 3002. As such, Table 2 shown below indicates the modifiedclass variables associated with storage devices 402 a-402 e:

TABLE 2 storage storage storage storage storage device device devicedevice device 402a 402b 402c 402d 402e Class Variable: 3 2 2 2 1

In step 3112, the first set of data pages is stored as a stripe in thefirst stripeset, including storing a data page of the first set of datapages in the third storage device. For example, the third data stripeprovided in step 3102 may be stored in first stripeset 3002. Forinstance, FIG. 32 shows a block diagram of data store 400 of FIG. 30,with the third data stripe provided in step 3102 stored in firststripeset 3002 as a third data stripe 3202. As shown in FIG. 32, firststripeset 3002 includes first-third data pages 3204 a-3204 c stored instorage devices 402 b-402 d (page slots 406 c, 408 c, and 410 b),respectively. Furthermore, third data stripe 3202 overlaps with seconddata stripe 3008, both having a data page stored in storage device 402d.

Thus, flowchart 3100 enables sliding window stripesets. Using slidingwindow stripesets, if a storage device of a first stripeset becomesfull, the first stripeset may advance by adding a next storage device ofthe data store to the first stripeset, even if the next storage deviceis included in a second stripeset. In an embodiment, the next storagedevice may be added to the first stripeset if the value of the classvariable of the first stripeset is greater than (or has other desiredrelationship with) the value of the class variable of the secondstripeset. In the above example, the value of the class variable offirst stripeset 3002 (“2”) is greater than (or has other desiredrelationship with) the value of the class variable of second stripeset3004 (“1”), and thus the class variable of storage device 402 d mayincremented, and storage device 402 d may be added to first stripeset3002 from second stripeset 3004.

If stripesets are arranged in this manner, stripesets can be representedby identifying the storage device ID of the first storage device of thehighest class and the storage device ID of the last storage device ofeach stripeset. The storage device ID of the last storage device mayalso serve to identify the lower bound of the next lower class. If thehighest class has a fixed, known rank, then the storage device ID of thefirst storage device of the highest class need not be indicated, becauseit can be calculated from the storage device ID of the last storagedevice of the highest class. In fact, any class whose stripeset has afixed rank can allow one of the stripeset boundaries to be dispensedwith.

Note that with regard to FIG. 32, because the value of the classvariable of storage device 402 d is no longer the class of secondstripeset 3004, a next append operation of the class of second stripeset3004 to storage devices 402 d and 402 e will fail, because storagedevice 402 d will reject the append operation. In such case, the deviceinvoking the append operation (e.g., computer 900) may respond bysliding second stripeset 3004. In such case, storage device 402 d isremoved from second stripeset 3004, and a next storage device in thelogical sequence may be added to second stripeset 3004, which is storagedevice 402 f (not actually shown in FIG. 32).

For instance, FIG. 33 shows a flowchart 3300 providing a process forstoring a data stripe, according to an example embodiment. Flowchart3300 may be performed subsequently to flowchart 3100 shown in FIG. 31,for instance. Flowchart 3300 may be performed by a device storing datain a data store, such as computer 900 shown in FIG. 9, and/or may beperformed by one or more storage devices in the data store. Furtherstructural and operational embodiments will be apparent to personsskilled in the relevant art(s) based on the discussion regardingflowchart 3300. Flowchart 3300 is described as follows.

As shown in FIG. 33, flowchart 3300 begins with step 3302. In step 3302,a second set of data pages is provided to be stored in the secondstripeset, the second stripeset including the third storage device. Forinstance, computer 900 (FIG. 9) (or other device) may provide a fourthdata stripe that includes a set of data pages to be stored in secondstripeset 3004 of FIG. 32.

In step 3304, the class variable of the third storage device isdetermined to be a higher class than the class of the second stripeset.The device providing the fourth data stripe may attempt to store a datapage of the fourth data stripe in storage device 402 d, which previouslyhad a class variable indicating a class of second stripeset 3004.However, storage device 402 d has a class variable indicating a class offirst stripeset 3002, which is a higher class than that of secondstripeset 3004.

In step 3306, the third storage device is removed from the secondstripeset. Because the class variable associated with storage device 402d has been raised (or otherwise modified) to be higher than the class ofsecond stripeset 3004, data stripes having a class indicator thatindicates the class of second stripeset 3004 can no longer be stored instorage device 402 d. Thus, storage device 402 d is removed from secondstripeset 3004.

In step 3308, a fourth storage device of the data store is added to thesecond stripeset. For example, as shown in FIG. 32, it may be desired toadd the next consecutive storage device 402 to second stripeset 3004 inthe logical sequence of storage devices 402 a-402 y, which is storagedevice 402 f (not visible in FIG. 32). If storage device 402 f has anassociated class variable indicating a lower class than the class ofsecond stripeset 3004, storage device 402 f may be added to secondstripeset 3004.

In step 3310, a class variable of the fourth storage device is changedto indicate the class of the second stripeset. For example, the classvariable of storage device 402 f, which previously indicated a classbelow that of second stripeset 3004, may be incremented (or otherwisemodified) to indicate the class of second stripeset 3004.

In step 3312, the second set of data pages is stored as a stripe in thesecond stripeset, including storing a data page of the second set ofdata pages in the fourth storage device. For example, the fourth datastripe provided in step 3302 may be stored in second stripeset 3004,including storing a data page of the fourth data stripe in storagedevice 402 f.

Note that if the data pages of the rejected append operation areunordered with respect to each other, the data page that was attemptedto be stored in storage device 402 d may be stored in storage device 402f Alternatively, the data pages may be shifted such that the data pagesintended to be consecutively stored in storage device 402 d and storagedevice 402 e are stored in storage device 402 e and storage device 402f, respectively. In such an embodiment, the device attempting to storethe data stripe transmits a new append operation that writes the stripeto the storage devices in the desired order. This may waste page slotsif the previous append operation that failed to store a data page instorage device 402 d stored a data page in a page slot of storage device402 e.

In an embodiment, to avoid wasted page slots, data pages are enabled tobe reordered in a stripe reference. For instance, each data page in astripe reference may include an index that indicates a position of thedata page in the data stripe. For example, for third data stripe 3202 inFIG. 32, a stripe reference might be an indicator for storage device 402b (e.g., “2”) and the vector [(1, 3), (2, 3), (3, 2)], where (1, 3)indicates that the first page of data stripe 3202 is stored in page slot3 of storage device 402 b, (2, 3) indicates that the second page of datastripe 3202 is stored in page slot 3 of storage device 402 c, and (3, 2)indicates that the third page of data stripe 3202 is stored in page slot2 of storage device 402 d. Thus, if data stripe 3202 was stored in thesame location, but with the data pages reordered, the reordering of thedata pages may be indicated in the vector of the stripe reference. Forexample, the stripe reference of “2” [(3, 3), (1, 3), (2, 2),] indicatesthat the third data page of data stripe 3202 is stored in the third pageslot of storage device 402 b, etc.

Thus, in an embodiment, a striping technique is provided where a firststripeset of a first, higher class is followed by a second stripeset ofa second, lower class. When one or more storage devices at the beginningof the first stripeset overflow, an equal number of storage devices areadded to the first stripeset from the second stripeset, thereby causingthe second stripeset to add an equal number of storage devices, etc., ina cascading fashion.

Flowchart 1900 in FIG. 19 may be adapted to determine an activestripeset in a data store that includes multiple classes. For example,the GetFirstNonEmpty operation described above (e.g., step 1902) may beperformed as described above. The GetActiveFromRange operation describedabove (e.g., step 1904) may be modified. If the class of a middlestorage device is the desired class, then it is returned. If the classof a middle storage device is less than the desired class, then theresult of GetActiveFromRange(low, mid) is returned. Otherwise the resultof GetActiveFromRange(mid, high) is returned. The GetStripesetFromActiveoperation (e.g., step 1906) is performed in a manner to determine therange of storage devices that are of the same class as the activestorage device returned by the GetActiveFromRange operation.

III. Further Example Embodiments

Data stripe storage interface module 902 (FIGS. 9, 20), storagecontroller 1304 (FIGS. 13, 16), class comparator 1602 (FIG. 16), storagecleaning module 1702 (FIG. 17), storage controller 1802 (FIG. 18),stripeset determiner module 2002 (FIGS. 20, 21), non-empty storagedevice determiner module 2102 (FIG. 21), active storage devicedeterminer module 2104 (FIG. 21), and active range determiner module2106 (FIG. 21) may be implemented in hardware, software, firmware, orany combination thereof. For example, data stripe storage interfacemodule 902, storage controller 1304, class comparator 1602, storagecleaning module 1702, storage controller 1802, stripeset determinermodule 2002, non-empty storage device determiner module 2102, activestorage device determiner module 2104, and/or active range determinermodule 2106 may be implemented as computer program code configured to beexecuted in one or more processors. Alternatively, data stripe storageinterface module 902, storage controller 1304, class comparator 1602,storage cleaning module 1702, storage controller 1802, stripesetdeterminer module 2002, non-empty storage device determiner module 2102,active storage device determiner module 2104, and/or active rangedeterminer module 2106 may be implemented as hardware logic/electricalcircuitry.

FIG. 34 depicts an exemplary implementation of a computer 3400 in whichembodiments of the present invention may be implemented. For instance,computers 102 a-102 c (FIG. 1), computer 900 (FIG. 9), and/or computer2000 (FIG. 20) may be implemented similarly to computer 3400, and mayinclude one or more features of computer 3400 and/or alternativefeatures. Computer 3400 may be a general-purpose computing device in theform of a conventional personal computer, a mobile computer, or aworkstation, for example, or computer 3400 may be a special purposecomputing device. The description of computer 3400 provided herein isprovided for purposes of illustration, and is not intended to belimiting. Embodiments of the present invention may be implemented infurther types of computer systems, as would be known to persons skilledin the relevant art(s).

As shown in FIG. 34, computer 3400 includes a processing unit 3402, asystem memory 3404, and a bus 3406 that couples various systemcomponents including system memory 3404 to processing unit 3402. Bus3406 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. System memory 3404 includes read onlymemory (ROM) 3408 and random access memory (RAM) 3410. A basicinput/output system 3412 (BIOS) is stored in ROM 3408.

Computer 3400 also has one or more of the following drives: a hard diskdrive 3414 for reading from and writing to a hard disk, a magnetic diskdrive 3416 for reading from or writing to a removable magnetic disk3418, and an optical disk drive 3420 for reading from or writing to aremovable optical disk 3422 such as a CD ROM, DVD ROM, or other opticalmedia. Hard disk drive 3414, magnetic disk drive 3416, and optical diskdrive 3420 are connected to bus 3406 by a hard disk drive interface3424, a magnetic disk drive interface 3426, and an optical driveinterface 3428, respectively. The drives and their associatedcomputer-readable media provide nonvolatile storage of computer-readableinstructions, data structures, program modules and other data for thecomputer. Although a hard disk, a removable magnetic disk and aremovable optical disk are described, other types of computer-readablemedia can be used to store data, such as flash memory cards, digitalvideo disks, random access memories (RAMs), read only memories (ROM),and the like.

A number of program modules may be stored on the hard disk, magneticdisk, optical disk, ROM, or RAM. These programs include an operatingsystem 3430, one or more application programs 3432, other programmodules 3434, and program data 3436. Application programs 3432 orprogram modules 3434 may include, for example, computer program logicfor implementing data stripe storage interface module 902, storagecontroller 1304, class comparator 1602, storage cleaning module 1702,storage controller 1802, stripeset determiner module 2002, non-emptystorage device determiner module 2102, active storage device determinermodule 2104, active range determiner module 2106, flowchart 500,flowchart 800, flowchart 1000, flowchart 1100, flowchart 1400, flowchart1500, flowchart 1900, flowchart 2200, flowchart 2400, flowchart 2500,flowchart 2700, flowchart 3100, and/or flowchart 3300 (including anystep of flowcharts 500, 800, 1000, 1100, 1400, 1500, 1900, 2200, 2400,2500, 2700, 3100, and 3300), and/or any further embodiments as describedabove.

A user may enter commands and information into the computer 3400 throughinput devices such as keyboard 3438 and pointing device 3440. Otherinput devices (not shown) may include a microphone, joystick, game pad,satellite dish, scanner, or the like. These and other input devices areoften connected to the processing unit 3402 through a serial portinterface 3442 that is coupled to bus 3406, but may be connected byother interfaces, such as a parallel port, game port, or a universalserial bus (USB).

A monitor 3444 or other type of display device is also connected to bus3406 via an interface, such as a video adapter 3446. In addition to themonitor, computer 3400 may include other peripheral output devices (notshown) such as speakers and printers.

Computer 3400 is connected to a network 3448 (e.g., the Internet)through a network adaptor or interface 3450, a modem 3452, or othermeans for establishing communications over the network. Modem 3452,which may be internal or external, is connected to bus 3406 via serialport interface 3442.

As used herein, the terms “computer program medium” and“computer-readable medium” are used to generally refer to media such asthe hard disk associated with hard disk drive 3414, removable magneticdisk 3418, removable optical disk 3422, as well as other media such asflash memory cards, digital video disks, random access memories (RAMs),read only memories (ROM), and the like.

As noted above, computer programs and modules (including applicationprograms 3432 and other program modules 3434) may be stored on the harddisk, magnetic disk, optical disk, ROM, or RAM. Such computer programsmay also be received via network interface 3450 or serial port interface3442. Such computer programs, when executed or loaded by an application,enable computer 3400 to implement features of embodiments of the presentinvention discussed herein. Accordingly, such computer programsrepresent controllers of the computer 3400.

The invention is also directed to computer program products comprisingsoftware stored on any computer useable medium. Such software, whenexecuted in one or more data processing devices, causes a dataprocessing device(s) to operate as described herein. Embodiments of thepresent invention employ any computer-useable or computer-readablemedium, known now or in the future. Examples of computer-readablemediums include, but are not limited to storage devices such as RAM,hard drives, floppy disks, CD ROMs, DVD ROMs, zip disks, tapes, magneticstorage devices, optical storage devices, MEMs, nanotechnology-basedstorage devices, and the like.

In another embodiment, a method includes: storing data that includes Mdata pages as a stripe in a stripeset of a data store, the stripesetincluding N storage devices; and generating a reference for the stripethat includes an identifier for a storage device of the N storagedevices in which a first data page of the M data pages is stored and avector that includes a page slot indicator for each of the M data pages,each page slot indicator indicating for a corresponding data page of theM data pages a page slot of a storage device of the N storage devices inwhich the corresponding data page is stored.

The N storage devices of the stripeset may be associated in a logicalsequence, the logical sequence including a first storage device of the Nstorage devices at a logical first end of the stripeset and a secondstorage device of the N storage devices at a logical second end of thestripeset. The storing may include: storing the first data page of the Mdata pages in the first storage device; and storing each subsequent datapage of the M data pages in a corresponding next consecutive storagedevice in the logical sequence from the first storage device.

The N storage devices of the stripeset may be associated in a logicalsequence, the logical sequence including a first storage device of the Nstorage devices at a logical first end of the stripeset and a secondstorage device of the N storage devices at a logical second end of thestripeset. The method may further include: determining that the firststorage device is full; removing the first storage device from thestripeset; and adding a next storage device of the data store to thestripeset to be logically positioned at the logical second end of thestripeset adjacent to the second storage device.

Each storage device may include a flash memory device.

In another embodiment, a method comprises: associating a class variablewith a corresponding storage device of a data store, the class variableindicating a store status of the corresponding storage device, the datastore including a plurality of storage devices having associated classvariables; enabling the class variable to be modified by a firstcomputer that stores a data page in the corresponding storage device;and enabling the class variable to be reset by a second computer thaterases data stored in the corresponding storage device.

In an embodiment, the enabling the class variable to be modified by acomputer that stores a data page in the corresponding storage devicecomprises: receiving a request from the first computer to store the datapage in the storage device, the request including a class indication;enabling the data page to be stored in a next available page slot of thestorage device if the class indication has a first relationship with theclass variable; enabling the data page to be stored in a next availablepage slot of the storage device and modifying the class variable if theclass indication has a second relationship with the class variable; andgenerating a response to the request that includes the class variable ifthe class indication has a third relationship with the class variable.

In an embodiment, the associating comprises: configuring the classvariable to have a first value to indicate that the correspondingstorage device is empty, a second value to indicate that thecorresponding storage device is active, or a third value to indicatethat the corresponding storage device is full.

In an embodiment, the associating comprises: configuring the classvariable to have a first value to indicate that the correspondingstorage device is empty, a second value to indicate that thecorresponding storage device is full, and a plurality of additionalvalues that each indicate a corresponding type of stripe data storablein the corresponding storage device.

In an embodiment, the method further comprises: incrementing the classvariable if the corresponding storage devices reaches a predeterminedfullness threshold.

In an embodiment, the method further comprises: storing at least onedata page that includes first data of a first data type in a storagedevice of the data store when the class variable has a first value;changing the class variable from the first value to a second valuerepresentative of a second data type; and storing at least one data pagethat includes second data of the second data type in the storage deviceof the data store.

In an embodiment, the data page is a data page of a data stripe.

In another embodiment, in a method for determining a stripeset in aplurality of storage devices in a data store, the plurality of storagedevices are associated in a logical sequence, the logical sequenceincluding a first storage device at a logical first end of the pluralityof storage devices and a second storage device at a logical second endof the plurality of storage devices, the method comprising: determininga logically closest non-empty storage device of the plurality of storagedevices to the logical first end; determining an active storage deviceof the plurality of storage devices in a range of the logical sequencefrom the logically closest non-empty storage device to the logicalsecond end; and determining a continuous range of active storage devicesin the plurality of storage devices that includes the determined activestorage device.

Each storage device of the plurality of storage devices may have anassociated epoch number that has an initial value and that is modifiedeach time the associated storage device is erased, and the determining alogically closest non-empty storage device of the plurality of storagedevices to the logical first end may include: indicating the firststorage device to be the logically closest non-empty storage device ifthe first storage device is non-empty; indicating that all of theplurality of storage devices are empty if the first and second storagedevices are empty and have a same epoch value; and performing a binarysearch over the logical sequence from the first storage device to thesecond storage device to determine a logically closest storage device tothe logical first end having an epoch number that is different from anepoch number of the first storage device.

The determining an active storage device of the plurality of storagedevices in a range of the logical sequence from the logically closestnon-empty storage device to the logical second end may include:indicating the logically closest non-empty storage device to be theactive storage device if the logically closest non-empty storage deviceis active; indicating the second storage device to be the active storagedevice if the second storage device is active and the logically closestnon-empty storage device is not active; and performing a binary searchover the logical sequence from the logically closest non-empty storagedevice to the second storage device to determine an active storagedevice.

The determining a continuous range of active storage devices in theplurality of storage devices that includes the determined active storagedevice may include: searching the plurality of storage devices in thelogical sequence from the determined active storage device towards thefirst storage device for a first non-active storage device; searchingthe plurality of storage devices in the logical sequence from thedetermined active storage device towards the second storage device for asecond non-active storage device; and indicating the continuous range ofactive storage devices to be a continuous range of storage devicesbetween the first non-active storage device and the second non-activestorage device.

In another embodiment, a method includes: providing a first set of datapages to be stored in a first stripeset of a data store, the firststripeset including M storage devices, the M storage devices of thefirst stripeset being associated in a logical sequence that includes afirst storage device of the M storage devices at a logical first end ofthe first stripeset and a second storage device of the M storage devicesat a logical second end of the first stripeset; determining that thefirst storage device is full; removing the first storage device from thefirst stripeset; adding a third storage device of the data store to thefirst stripeset, the third storage device of the data store having anassociated class variable that indicates a class of a second stripesetof the data store; changing the class variable to indicate a class ofthe first stripeset; and storing the first set of data pages as a stripein the first stripeset, including storing a data page of the first setof data pages in the third storage device.

The method may further include: providing a second set of data pages tobe stored in the second stripeset, the second stripeset including thethird storage device; determining that the class variable of the thirdstorage device is a higher class than the class of the second stripeset;removing the third storage device from the second stripeset; adding afourth storage device of the data store to the second stripeset;changing a class variable of the fourth storage device to indicate theclass of the second stripeset; and storing the second set of data pagesas a stripe in the second stripeset, including storing a data page ofthe second set of data pages in the fourth storage device.

IV. Conclusion

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexample only, and not limitation. It will be understood by those skilledin the relevant art(s) that various changes in form and details may bemade therein without departing from the spirit and scope of theinvention as defined in the appended claims. Accordingly, the breadthand scope of the present invention should not be limited by any of theabove-described exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

What is claimed is:
 1. A method, comprising: receiving an indication ofa first set of data pages to be stored in a first stripeset of a datastore, the first stripeset including M storage devices, the M storagedevices of the first stripeset being associated in a logical sequencethat includes a first storage device of the M storage devices at alogical first end of the first stripeset and a second storage device ofthe M storage devices at a logical second end of the first stripeset;determining that the first storage device is full; removing the firststorage device from the first stripeset; adding a third storage deviceof the data store to the first stripeset, the third storage device ofthe data store having an associated class variable that indicates aclass of a second stripeset of the data store; changing the classvariable to indicate a class of the first stripeset; and storing thefirst set of data pages as a stripe in the first stripeset, includingstoring a data page of the first set of data pages in the third storagedevice.
 2. The method of claim 1, further comprising: receiving anindication of a second set of data pages to be stored in the secondstripeset, the second stripeset including the third storage device;determining that the class variable of the third storage device is ahigher class than the class of the second stripeset; removing the thirdstorage device from the second stripeset; adding a fourth storage deviceof the data store to the second stripeset; changing a class variable ofthe fourth storage device to indicate the class of the second stripeset;and storing the second set of data pages as a stripe in the secondstripeset, including storing a data page of the second set of data pagesin the fourth storage device.
 3. The method of claim 1, wherein saidstoring comprises: enabling the data page of the first set of data pagesto be stored in the third storage device if a class indication includedin the request has a first relationship with the class variable of thethird storage device.
 4. The method of claim 1, further comprising:configuring the class variable to have a first value to indicate thatthe third storage device is empty, a second value to indicate that thethird storage device is active, or a third value to indicate that thethird storage device is full.
 5. The method of claim 1, furthercomprising: configuring the class variable to have a first value toindicate that the third storage device is empty, a second value toindicate that the third storage device is full, and a plurality ofadditional values that each indicate a corresponding type of stripe datastorable in the third storage device.
 6. The method of claim 1, furthercomprising: incrementing the class variable if the third storage devicereaches a predetermined fullness threshold.
 7. The method of claim 1,further comprising: enabling storage of data pages that include data ofa first data type in the third storage device when the class variablehas a first value; and enabling storage of data pages that include dataof a second data type in the third storage device when the classvariable has a second value.
 8. A system, comprising: a data storecomprising a plurality of storage devices; at least one processorcircuit; and a memory that stores program code configured to be executedby the at least one processor circuit to perform operations, theoperations including: receiving an indication of a first set of datapages to be stored in a first stripeset of the data store, the firststripeset including M storage devices of the plurality of storagedevices, the M storage devices of the first stripeset being associatedin a logical sequence that includes a first storage device of the Mstorage devices at a logical first end of the first stripeset and asecond storage device of the M storage devices at a logical second endof the first stripeset; determining that the first storage device isfull; removing the first storage device from the first stripeset; addinga third storage device of the data store to the first stripeset, thethird storage device of the data store having an associated classvariable that indicates a class of a second stripeset of the data store;changing the class variable to indicate a class of the first stripeset;and storing the first set of data pages as a stripe in the firststripeset, including storing a data page of the first set of data pagesin the third storage device.
 9. The system of claim 8, wherein theoperations further comprise: receiving an indication of a second set ofdata pages to be stored in the second stripeset, the second stripesetincluding the third storage device; determining that the class variableof the third storage device is a higher class than the class of thesecond stripeset; removing the third storage device from the secondstripeset; adding a fourth storage device of the data store to thesecond stripeset; changing a class variable of the fourth storage deviceto indicate the class of the second stripeset; and storing the secondset of data pages as a stripe in the second stripeset, including storinga data page of the second set of data pages in the fourth storagedevice.
 10. The system of claim 8, wherein said storing comprises:enabling the data page of the first set of data pages to be stored inthe third storage device if a class indication included in the requesthas a first relationship with the class variable of the third storagedevice.
 11. The system of claim 8, wherein the operations furthercomprise: configuring the class variable to have a first value toindicate that the third storage device is empty, a second value toindicate that the third storage device is active, or a third value toindicate that the third storage device is full.
 12. The system of claim8, wherein the operations further comprise: configuring the classvariable to have a first value to indicate that the third storage deviceis empty, a second value to indicate that the third storage device isfull, and a plurality of additional values that each indicate acorresponding type of stripe data storable in the third storage device.13. The system of claim 8, wherein the operations further comprise:incrementing the class variable if the third storage device reaches apredetermined fullness threshold.
 14. The system of claim 8, wherein theoperations further comprise: enabling storage of data pages that includedata of a first data type in the third storage device when the classvariable has a first value; and enabling storage of data pages thatinclude data of a second data type in the third storage device when theclass variable has a second value.
 15. A computer-readable storagemedium comprising computer-executable instructions that, when executedby a processor, perform a method comprising: receiving an indication ofa first set of data pages to be stored in a first stripeset of a datastore, the first stripeset including M storage devices, the M storagedevices of the first stripeset being associated in a logical sequencethat includes a first storage device of the M storage devices at alogical first end of the first stripeset and a second storage device ofthe M storage devices at a logical second end of the first stripeset;determining that the first storage device is full; removing the firststorage device from the first stripeset; adding a third storage deviceof the data store to the first stripeset, the third storage device ofthe data store having an associated class variable that indicates aclass of a second stripeset of the data store; changing the classvariable to indicate a class of the first stripeset; and storing thefirst set of data pages as a stripe in the first stripeset, includingstoring a data page of the first set of data pages in the third storagedevice.
 16. The computer-readable storage medium of claim 15, whereinthe method further comprises: receiving an indication of a second set ofdata pages to be stored in the second stripeset, the second stripesetincluding the third storage device; determining that the class variableof the third storage device is a higher class than the class of thesecond stripeset; removing the third storage device from the secondstripeset; adding a fourth storage device of the data store to thesecond stripeset; changing a class variable of the fourth storage deviceto indicate the class of the second stripeset; and storing the secondset of data pages as a stripe in the second stripeset, including storinga data page of the second set of data pages in the fourth storagedevice.
 17. The computer-readable storage medium of claim 15, whereinsaid storing comprises: enabling the data page of the first set of datapages to be stored in the third storage device if a class indicationincluded in the request has a first relationship with the class variableof the third storage device.
 18. The computer-readable storage medium ofclaim 15, wherein the method further comprises: configuring the classvariable to have a first value to indicate that the third storage deviceis empty, a second value to indicate that the third storage device isactive, or a third value to indicate that the third storage device isfull.
 19. The computer-readable storage medium of claim 15, wherein themethod further comprises: configuring the class variable to have a firstvalue to indicate that the third storage device is empty, a second valueto indicate that the third storage device is full, and a plurality ofadditional values that each indicate a corresponding type of stripe datastorable in the third storage device.
 20. The computer-readable storagemedium of claim 15, wherein the method further comprises: enablingstorage of data pages that include data of a first data type in thethird storage device when the class variable has a first value; andenabling storage of data pages that include data of a second data typein the third storage device when the class variable has a second value.